mcp-front is a reverse proxy/auth gateway for MCP servers, not a traditional MCP tool server. The 4 test tools (echo_text, sample_stream, get_time, echo_streamable) are mock fixtures in JavaScript, not actual production tools. All 4 tools have minimal, generic descriptions (7-26 chars) far below the 34-char p10 baseline. None have parameter descriptions. Schemas are present but trivial, most parameters are optional or empty. The server's primary function is proxying and authenticating requests to upstream MCP servers, not providing domain-specific tools. Tool definitions appear in mock test fixtures (mock-sse-server.js, mock-streamable-server.js), not in the Go application code. This is a protocol implementation test harness, not a tool-rich MCP server.

• Expand all 4 tool descriptions to 50-200 chars, explaining: what the tool does, when to call it, what it returns, and how it differs from related tools. Example: 'echo_text' → 'Echoes back the provided text string unchanged. Use this to test text round-trip behavior. Returns {content: [{type: "text", text: "<echoed input>"}]}'
• Add parameter descriptions for 'text' in echo_text and echo_streamable: 'The text string to echo (any length, any characters). Will be returned verbatim in the response.'
• Document output schemas for all tools. Example: echo_text output: {type: 'object', properties: {content: {type: 'array', items: {type: 'object', properties: {type: {type: 'string'}, text: {type: 'string'}}}}}}
• Move tool definitions from mock JavaScript fixtures into the main Go server code, or clarify in docs that these are test fixtures only. If mcp-front is a proxy, define its actual capabilities (pass-through, no local tools) rather than exposing mock fixtures.
• For sample_stream and get_time (which take no parameters), add descriptions of the streaming data structure and interval. Example: 'Returns a stream of {timestamp: ISO8601, delay_ms: number} events every N seconds.'
• Add error handling guidance: return 'Tool not found: <name>. Available tools: echo_text, sample_stream, get_time, echo_streamable' on unknown tool errors, not bare JSON-RPC -32601.

Inferred effective spec: <=2025-11-25.

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