Skip to main content
Glama

Facts about a package on npm, PyPI or crates.io: latest

package
Read-only

Facts about a package on npm, PyPI or crates.io: latest version and date, license, description, repository, maintainers (npm), weekly downloads (npm), a deprecated or yanked flag, and how many known vulnerabilities the latest version has (OSV). Related tools on this server, for a different need: package_search when you need to search npm, crates, Packagist, RubyGems and NuGet packages. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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": "package"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesPackage name
ecosystemYesnpm, pypi or crates

Output Schema

NameRequiredDescriptionDefault
nameNo
sourceNo
licenseNo
checkedAtNo
ecosystemNo
deprecatedNo
repositoryNo
descriptionNo
maintainersNo
publishedAtNo
latestVersionNo
vulnerabilitiesNo
weeklyDownloadsNo
deprecationMessageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations cover only readOnlyHint and openWorldHint, so the description's cost model adds real value: $0.002 per successful call, paid via x402 with USDC on Base and other networks, with failed calls not charged. That is a prepay/pricing constraint an agent cannot get from structured fields, and it does not contradict the read-only annotation.

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?

Purpose is front-loaded, followed by the alternative tool and the price, in a logical order. The middle clause is a long enumerated list that could be tightened, but each element is substantive rather than filler.

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

Completeness5/5

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

For a two-parameter lookup with an output schema, the definition covers what is returned, which registries are supported, when to use the sibling instead, and the billing behavior. There is no material gap an agent would need to close before calling it.

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 coverage is 100% and both parameters (name, ecosystem) are already described in the schema, so the baseline is 3. The description does add that some returned fields are ecosystem-specific (maintainers and weekly downloads are npm-only), which hints at output shape but not at input syntax or accepted ecosystem values beyond what the schema states.

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

Purpose5/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 framing and then enumerates exactly what facts are returned: latest version and date, license, repository, maintainers, weekly downloads, deprecation/yank flag, and OSV vulnerability count. It also scopes the registries (npm, PyPI, crates.io), making it distinguishable from package_search, which covers a different set of registries.

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

Usage Guidelines4/5

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

It explicitly names the sibling to use for a different need — package_search for searching npm, crates, Packagist, RubyGems and NuGet — which gives a clear routing rule. It does not state outright that this tool is for when you already know the exact package name, so the selection criterion is inferred rather than spelled out.

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