A Go SDK for building Model Context Protocol (MCP) servers and clients with support for multiple transport types (HTTP, WebSocket, stdio)
This is an MCP SDK/framework, not a deployable MCP server with production tools. The three tools shown (test-tool, calculator, echo) are minimal examples embedded in test and example files, not primary server implementations. Tool definitions are inferred from test/example code rather than explicitly registered in a main server codebase. Descriptions exist but are extremely generic (10-45 chars). Input schemas are present but minimally documented, parameters lack depth and context. The SDK itself shows good Go engineering (error handling, session management, type safety via generics), but the bundled example tools do not meet production quality standards for an MCP server. The framework supports prompts, resources, and logging, but tools are underdeveloped.
Calculator tool for performing arithmetic operations
Echo tool that returns the provided arguments
A test tool
Tool naming does not follow verb_noun convention. 'test-tool' is generic and does not convey action. 'echo' is vague about purpose (echo what? to where?). Only 'calculator' hints at a clear operation.
Descriptions are below the 10-char minimum for clarity. 'A test tool' (11 chars) and 'Echo tool that returns the provided arguments' (45 chars) lack context for when/why an LLM should select them. No indication of prerequisites, return value structure, or use cases.
Parameter descriptions are missing or trivial. 'echo' has parameters with type 'object' for nested data but no description of its structure or contents. 'calculator' parameter descriptions are minimal ('The operation to perform...') without enums or format constraints.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | F | 35 | <=2025-11-25 | v2 |
| 2026-03-09 | F | 35 | - | v1 |
Input schemas lack constraints. 'operation' in calculator should be an enum (add|subtract|multiply|divide), not a free-form string. 'a' and 'b' have no min/max bounds, LLMs could pass 10^100 or negative infinity.
Output schemas are not documented. What does 'calculator' return, a number, an object with result+timestamp, an error message on division by zero? What does 'echo' return? LLMs cannot plan downstream calls without knowing return structure.
Error handling is absent or opaque. No indication of how tools fail, whether errors are retryable, or what recovery steps to take. 'calculator' dividing by zero is undefined in the tool contract.
Tools are defined in test and example files (.go test files), not in a main server module. This is a framework, not a ready-to-deploy server.