@manywe/mcp-tools

Provides TypeScript-first tool definition system that generates Model Context Protocol (MCP) compliant tool schemas with type safety. Uses TypeScript interfaces and decorators to define tool signatures, parameters, and return types that are automatically serialized into MCP tool definition format for agent consumption. Enables declarative tool registration with built-in validation of parameter schemas and tool metadata.

Acts as a bridge layer between MCP tool definitions and ManyWe Agent runtime, handling tool discovery, parameter marshalling, and result serialization. Implements the MCP protocol handshake to register tools with the agent, manages tool invocation lifecycle, and handles error propagation from tool execution back to the agent. Supports both synchronous and asynchronous tool execution with timeout and retry semantics.

Automatically validates tool invocation parameters against TypeScript-defined schemas before execution, using JSON schema validation with support for complex types (unions, arrays, nested objects). Generates human-readable validation error messages that help agents understand parameter requirements. Supports custom validators and coercion rules for common type conversions (string-to-number, ISO date parsing, etc.).

Automatically extracts tool descriptions, parameter documentation, and usage examples from TypeScript definitions and JSDoc comments to generate human-readable tool documentation. Creates structured metadata (name, description, category, tags) that helps agents understand tool purpose and when to invoke them. Supports markdown formatting in descriptions for rich documentation rendering in agent interfaces.

Provides utilities for composing multiple tools into higher-level tool workflows, including sequential execution, conditional branching, and parallel tool invocation patterns. Implements tool composition as first-class abstractions that agents can invoke as single tools, abstracting away orchestration complexity. Supports passing outputs from one tool as inputs to subsequent tools with automatic type checking.

Supports multiple versions of the same tool with automatic routing to appropriate implementation based on agent compatibility requirements. Tracks tool schema changes and provides migration utilities for updating tool definitions without breaking existing agent integrations. Enables gradual rollout of tool updates with version-specific parameter handling and deprecation warnings.

Manages execution context for tool invocations including agent identity, request metadata, user information, and request-scoped state. Provides context propagation through tool call chains so nested tools can access parent context without explicit parameter passing. Implements context isolation to prevent state leakage between concurrent tool invocations and supports context cleanup on tool completion.