A Model Context Protocol (MCP) server for Go development that exposes tools for retrieving Go documentation and other Go-related utilities.
This MCP server exposes 2 tools with moderate description quality but significant schema and parameter annotation gaps. The 'hello' tool is trivial (no parameters, minimal context). The 'godoc' tool has a lengthy description (286 chars) that exceeds typical annotation length but lacks formal parameter type definitions in the visible schema. Input schemas are inferred from cli/main.go code (where arguments are constructed as map[string]any) rather than explicitly registered with type information. The server/main.go shows tools registered via mcp.AddTool() with Name and Description, but no explicit JSON Schema or input parameter definitions are visible in the source. Per the hard rules, lack of visible input schemas means schema scores cannot exceed 0. Descriptions are present but lack the constraint details, error guidance, and multi-step context needed for reliable LLM tool selection.
Retrieves Go documentation for a given package or symbol using the `go doc` command. This tool is useful for understanding Go's standard library APIs, third-party libraries, and even your own codebase without needing to consult external websites or IDEs. The output of this tool is the raw text output of the `go doc` command. This may include the package name, import path, a description of the package, and a list of functions, types, and variables. Arguments: - `package`: The name of the Go package to document (e.g., `fmt`, `net/http`). This argument is required. - `symbol`: The name of the symbol (function, type, variable) to document within the package (e.g., `Println`, `Request`). This argument is optional. Example: To get the documentation for the `Println` function in the `fmt` package, you would call the tool with `package`='fmt' and `symbol`='Println'.
A simple hello world tool.
No visible JSON Schema input definitions. Tools registered with Name and Description only; no explicit JSON Schema with typed parameters and constraints visible in server/main.go.
'hello' tool is trivial and provides no context for LLM selection. Description reads as a placeholder ('A simple hello world tool.') and offers no information about when or why to call it.
'godoc' description (286 chars) includes example values ('fmt', 'Println') and manually formatted argument documentation. Move examples to formal schema; use parameter descriptions for constraints.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 38 | 2026-07-28+ | v2 |
Parameter 'symbol' is optional per description, but no default behavior or skip-handling guidance is provided. If symbol is empty, what does godoc output? How should the LLM know to omit it vs. pass an empty string? Undocumented dependency.
No output schema documented for either tool. LLMs cannot plan downstream actions or extract structured data. Both tools return raw text (mcp.TextContent), but structure, size limits, and field mapping are not documented.
No error handling guidance. What happens if godoc fails (invalid package name, symbol not found, go doc subprocess crashes)? Descriptions do not document error cases or recovery paths. Per pattern: errors must tell LLM what to do next.
'hello' tool has empty input schema (Input: {}). No parameters, no way to customize behavior. Tool is read-only and stateless but lacks idempotent/readOnlyHint annotation in the visible code.