mcpd is a meta-MCP server (a proxy/gateway for discovering and calling other MCP servers). It has 3 tools with moderate-to-good naming and descriptions, but lacks critical schema documentation and parameter descriptions. Tools are visible in internal/api/tools.go and internal/api/servers.go. All tools have basic descriptions (68 - 106 chars), meeting the 10 - 1024 char range, but parameter details are sparse. The 'callTool' tool accepts an open-ended 'body' object with no schema constraints, which is a high-risk pattern for composition. Output schemas are not documented anywhere in the provided source. Tool names follow verb_noun convention (listTools, callTool, listServers), which is good. However, parameter descriptions are either missing or minimal, violating the pattern:tool-description requirement. This server would benefit from explicit JSON Schema definitions for all parameters and documented output schemas.

• Add explicit JSON Schema definitions for the 'body' parameter in callTool. Example: {"type": "object", "additionalProperties": true, "description": "Arguments to pass to the remote tool. Structure depends on the target tool's input schema. Use listTools(detail='full') to discover the target tool's schema first."}
• Document output schemas for all three tools. For listTools, specify: {"tools": [{"name": string, "description": string, "inputSchema": object}]}. For callTool, specify the passthrough response format. For listServers, specify: {"servers": [{"name": string, "status": "running"|"stopped", ...}]}.
• Add descriptions to parameters lacking them. For 'server' in callTool: 'The name of the registered MCP server to target (e.g., "filesystem", "github"). Use listServers() to discover available servers.' For 'tool': 'The name of the tool on the target server to invoke (e.g., "read_file"). Use listTools(server=..., detail="full") to discover available tools and their schemas.'
• Expand callTool description to include a recovery guide. Example: 'Calls a tool on a specified remote MCP server. If the remote tool is not found, use listTools(server=..., detail="full") to discover available tools. If the call fails, check error details and retry with corrected arguments or try an alternative tool.'
• Add permission checks and rate limiting to callTool. Document what permissions are required (e.g., 'requires agent:execute-remote-tool scope') and mention rate limits (e.g., 'Limited to 100 calls per minute per server').

Inferred effective spec: 2025-06-18+.

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry