A Go implementation of the Model Context Protocol (MCP) server with support for tools, resources, and prompts
mcp-go provides 5 tools with basic schemas and descriptions, but quality is inconsistent. Tool 'notify' has NO description (critical gap). 'getTinyImage' description is trivial (11 chars). Parameter descriptions are present but minimal (avg ~20 chars, well below the 72-char baseline). Schemas are properly typed (object with properties/required), but lack depth, no enums, patterns, or constraints. No output schemas documented. Error handling is absent from tool definitions. The framework itself is well-structured (functional options pattern for tool building), but tool definitions do not leverage it fully.
Adds two numbers
Echoes back the input
Returns the MCP_TINY_IMAGE
Demonstrates a long running operation with progress updates
Tool 'notify' has no description. LLMs cannot determine when or why to select it.
Tool 'getTinyImage' has trivial description (11 chars: 'Returns the MCP_TINY_IMAGE'). Fails to explain purpose, when to use, or what the image is used for.
No output schemas documented for any tool. LLMs cannot plan downstream calls or extract required fields.
Parameter descriptions are minimal (avg ~20 chars vs 72-char baseline). E.g., 'message' → 'Message to echo' lacks context on format, length, or constraints.
Inferred effective spec: 2025-06-18+.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 49 | 2025-06-18+ | v2 |
No enums, patterns, or constraints in schemas. E.g., 'duration' and 'steps' in longRunningOperation lack min/max bounds, inviting invalid values.