Skip to main content
Glama

resolve_exact_version

Read-onlyIdempotent

Verify one exact package version and symbol against its official commit. Never substitutes another version.

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": {
      "package": "<package>",
      "version": "<version>",
      "symbol": "<symbol>"
    },
    "name": "resolve_exact_version"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYes
packageYes
versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds a real behavioral guarantee beyond them — no fuzzy matching or fallback to a nearby version — but says nothing about what happens on a failed verification (error vs. negative result) or what source constitutes the 'official commit'.

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?

Two short sentences with no filler; the core action is front-loaded and the no-substitution constraint follows immediately as a qualifier. Every clause carries information.

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?

Annotations cover the safety profile, which lowers the burden, and there is no output schema to explain. However, for a verification tool the crucial missing piece is what a successful result looks like (a resolved commit hash? a boolean?) and how a failed verification is reported, plus what 'symbol' means — none of which appears in the description or the undocumented parameters.

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?

Schema description coverage is 0%, so the three required parameters (package, version, symbol) carry only regex patterns and lengths. The description partially compensates by naming all three concepts and by qualifying 'version' as exact, which is meaningful semantic guidance, but it never explains what a 'symbol' is in this domain or what form the version string takes beyond the pattern.

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 gives a specific verb and resource: 'Verify one exact package version and symbol against its official commit.' That is clearly distinct from a comparison or coverage-listing operation, and the closing clause 'Never substitutes another version' reinforces the single-version scope. It stops short of naming a sibling, so differentiation is inferred rather than stated.

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

Usage Guidelines3/5

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

Usage is implied by the phrase 'Verify one exact package version,' which signals a single-target lookup rather than a multi-version comparison; the no-substitution clause implies the tool is meant for strict pin verification. There is no explicit when-to-use vs. when-not guidance and no named alternative for cases where the user has an approximate or range version.

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.

Resources