Skip to main content
Glama

Package Latest Version Check

Check a package version

check_version
Read-onlyIdempotent

Is this version real, yanked, and how far behind latest (major versions released since)?

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": {
      "ecosystem": "<ecosystem>",
      "name": "<name>",
      "version": "<version>"
    },
    "name": "check_version"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
versionYes
ecosystemYes

Output Schema

NameRequiredDescriptionDefault
latestYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and closed-world behavior, so safety is covered. The description usefully discloses the three result facets it evaluates, but leaves open what happens on a nonexistent or invalid version (error vs. a 'real: false' result) and what 'yanked' means per ecosystem. With an output schema present, this is an acceptable but not rich disclosure.

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

Conciseness4/5

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

A single front-loaded sentence with no filler, which is appropriate for a simple lookup tool. The parenthetical '(major versions released since)' is slightly cryptic and reads like a footnote rather than a clear definition.

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?

The tool is simple, read-only, and ships an output schema, so return-value detail is not required. Still, the definition omits ecosystem options, version-format expectations, and failure behavior for nonexistent versions, leaving real gaps for a three-required-parameter tool with undocumented parameters.

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 description coverage is 0% for all three required parameters, so the description carries the burden and does not meet it: it never mentions the ecosystem parameter or its npm/pypi enum, says nothing about the name field, and gives no hint about accepted version syntax (semver vs PEP 440) or how comparison is performed.

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 names a concrete check on a package version and enumerates the three things it determines: whether the version exists, whether it is yanked, and how many major versions behind latest it is. The question phrasing is slightly informal and it never names or contrasts with the sibling latest_version, so differentiation relies on inference.

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?

There is no explicit when-to-use guidance, no mention of when not to use it, and no reference to latest_version as the alternative for simply retrieving the newest version. The implied use case (validating a specific version) must be inferred from the question wording.

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