versionator-mcp

get_go_module

Retrieve the latest version of a Go module by providing its module path. Returns version details from the Go module registry.

Instructions

Get the latest version of a Go module.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "module_path": "<module_path>"
    },
    "name": "get_go_module"
  }
}

Input Schema

Name	Required	Description	Default
`module_path`	Yes	The Go module path (e.g., "github.com/gin-gonic/gin")

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.3.1Jul 30, 2026

TDQS

B3.1/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description must disclose behavioral traits. It only states 'Get the latest version', which is a read operation, but does not mention error handling (e.g., if module not found), return format beyond 'version', or any authentication requirements. The presence of an output schema helps but the description adds little transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, direct sentence with no extraneous information. It is concise and front-loaded, achieving its communicative purpose efficiently.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple tool with one parameter and an output schema, the description is minimally adequate. However, given the presence of many sibling tools (including generic get_package_version), some contextual guidance on when to use this specific tool would enhance completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% coverage with a clear description for the sole parameter 'module_path'. The tool description adds no additional meaning beyond the schema, so the baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Get the latest version') and the resource ('Go module'). The tool name and description differentiate it from sibling tools targeting different ecosystems (e.g., npm, Python). However, no explicit distinction between this and the generic get_package_version tool is made, though the name implies specificity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives like get_package_version. An agent might not know if this tool is preferable for Go modules specifically. There is also no advice on prerequisites or common pitfalls.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.