Skip to main content
Glama

Module

module
Read-onlyIdempotent

Most recent version + metadata.

Input Schema

NameRequiredDescriptionDefault
module_pathYes

Output Schema

NameRequiredDescriptionDefault
TimeNoTimestamp of the version
VersionNoThe latest version string

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "module_path": "github.com/sirupsen/logrus"
      +  },
      +  {
      +    "module_path": "golang.org/x/net"
      +  }
      +]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "description": "Most recent version and metadata for a Go module",
      +  "properties": {
      +    "Time": {
      +      "description": "Timestamp of the version",
      +      "type": "string"
      +    },
      +    "Version": {
      +      "description": "The latest version string",
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
  2. First observed

TDQS

C2.1/5.0
Behavior3/5

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

Annotations already declare readOnly, openWorld, idempotent, and non-destructive behavior. The description adds no behavioral context beyond stating the output, which is adequate but not enhanced. No contradictions.

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

Conciseness3/5

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

The description is very concise at four words, but this conciseness sacrifices clarity. It is front-loaded but too minimal to be informative, failing to earn its place with meaningful content.

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

Completeness2/5

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

Despite an output schema and good annotations, the description lacks context about the tool's domain (e.g., Go modules) and how it differs from similar tools. It is incomplete for an agent to confidently select and use it.

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

Parameters2/5

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

Schema coverage is 0% with no property descriptions. The description mentions 'most recent version' which implies module_path identifies a module, but it does not clarify the expected format (e.g., Go module path) or add meaning beyond the raw parameter name.

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

Purpose2/5

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

The description 'Most recent version + metadata' vaguely implies retrieval but is not a clear verb-resource statement. It does not distinguish from sibling tools like go_mod or versions, making the tool's specific purpose ambiguous.

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

Usage Guidelines1/5

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

The description provides no guidance on when to use this tool versus alternatives such as go_mod, versions, or version_info. No context about prerequisites or limitations is given.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.