A Rust library for running and interacting with Model Context Protocol (MCP) servers locally
This server exposes only 2 tools, both with critical definition gaps. The 'initialize' tool appears to be a lifecycle management operation, not a proper MCP tool. The 'tools/list' tool has a slash in its name (violating naming conventions) and lacks any visible input schema or parameter documentation. Neither tool has documented output schemas. The codebase shows handlers.rs with minimal tool registration metadata, no explicit JSON Schema definitions, no parameter type systems, and descriptions are placeholder-level.
Initialize the MCP client connection to the server
List all available tools from all configured MCP servers
No input schemas visible for either tool. Tools register with descriptions only; JSON Schema input/output definitions are absent from src/sse_proxy/handlers.rs.
Tool name 'tools/list' violates verb_noun naming convention. The slash character breaks standard naming patterns and is not a valid MCP tool name (should be 'list_tools'). This confuses LLM parsing.
'initialize' is a lifecycle operation, not a tool. MCP protocol handles lifecycle via the initialize handshake in the protocol layer. Exposing it as a user-callable tool is incorrect design and suggests misunderstanding of MCP semantics.
Tool descriptions are single short sentences (10-40 chars) with minimal context. No mention of when to call the tool, what it returns, or dependencies. Below the 50 - 200 char baseline for A-grade tools.
Inferred effective spec: 2025-06-18+.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | F | 29 | 2025-06-18+ | v2 |
| 2026-03-09 | F | 27 | - | v1 |
No documented output schemas. LLMs cannot plan downstream calls or extract required fields (e.g., tool_id, description, parameters) from list_tools response.
No parameter validation or constraints documented. Even list_tools likely accepts query/filter params (limit, offset) that are not described.