Skip to main content
Glama

Package Latest Version Check

Latest version of a package

latest_version
Read-onlyIdempotent

Current latest version of an npm or PyPI package, its date, and the deprecation message if the latest is deprecated.

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>"
    },
    "name": "latest_version"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
ecosystemYes

Output Schema

NameRequiredDescriptionDefault
latestYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, and closed-world behavior, so safety is covered without the description. The description adds that a deprecation message is returned when the latest version is deprecated, which is useful beyond the structured data, but says nothing about behavior when the package is missing or about cross-ecosystem name handling.

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?

A single front-loaded sentence with no filler; every clause (version, date, deprecation) carries meaning about the return payload.

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

Completeness4/5

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

For a two-required-parameter lookup with an output schema and full annotation coverage, the description says enough to call it: both inputs are implied and the returned fields are enumerated. Only the not-found / error path and package-name formatting conventions are absent.

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 description must compensate, and it only partially does: 'npm or PyPI package' hints at the ecosystem enum values and that 'name' is the package name. It adds no detail on name format, scoped npm packages, case normalization, or the 214-character limit already present in the schema.

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?

Names a specific resource and retrieves a well-scoped result set: the current latest version, its date, and any deprecation message for npm or PyPI packages. It does not differentiate itself from the sibling check_version, so an agent cannot tell from this text alone which lookup tool to pick.

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 or when-not-to-use guidance and no mention of the sibling check_version, which the name suggests may overlap. The purpose implies the use case, but the agent is left to infer it.

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