MCP server providing access to pkg.go.dev API for searching and retrieving information about Go packages, modules, symbols, versions, vulnerabilities, and import relationships
8 tools with complete schemas and consistent descriptions. All tools are READ_ONLY and well-structured. Naming follows verb_noun pattern (search, get module/package info, list packages/symbols/versions, find imported-by, check vulns). Descriptions are clear (avg ~100 chars) and explain WHAT each tool does. However, parameter descriptions lack actionable constraints (no enums, ranges, or format specs). Output schemas are not documented, LLMs cannot predict response structure. Error handling is absent from visible code. No tool annotations (readOnlyHint present in metadata but not in schema). Pagination support is present (limit, token, filter) but underdocumented.
Paths of packages that import the package at {path}, excluding packages in the same module.
Information about the module at {path}.
Information about the package at {path}, optionally including rendered documentation.
Packages of the module at {path}. Results whose path or synopsis match the filter regexp are returned.
Search pkg.go.dev for packages. Results whose path or synopsis match the filter regexp are returned.
Symbols (functions, types, etc.) for the package at {path}. Results matching the filter regexp are returned.
Versions of the module at {path}, in descending order. Results matching the filter regexp are returned.
Output schemas not documented. LLMs cannot predict response structure (fields, types, pagination format). Forces agents to guess at downstream field names.
Parameter descriptions lack actionable constraints. 'version' accepts 'semantic version, latest, or default branch' but no enum or pattern. 'filter' accepts regex but no examples or format spec. LLMs cannot validate inputs before calling.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 64 | 2026-07-28+ | v2 |
Known vulnerabilities of the module or package at {path}, from the Go vulnerability database.
No error handling guidance in visible code. If API returns 404 (package not found) or 400 (invalid regex in filter), LLM receives raw error with no recovery hint. Should return 'Package not found. Try search_packages() first.' or 'Invalid regex in filter: <error>. Use simple substring match instead.'
Tool annotations missing from schema. All tools are READ_ONLY (no side effects), but readOnlyHint is not declared in InputSchema. Agents cannot infer safety without explicit annotation.
Pagination parameters (limit, token, filter) present but underdocumented. No guidance on default limit, max limit, or token format. 'filter' is described as regex but LLMs may pass invalid patterns. Should specify: 'limit: 1 - 100, default 20' and 'filter: Go regex syntax, e.g. ^github\.com/spf13'.