Skip to main content
Glama

package_info

Read-only

Fetch current version and key facts for an npm, PyPI, crates, or GitHub package/repo by name. Specify the registry to get accurate package metadata.

Instructions

Current version and facts of a package (npm, pypi, crates) or GitHub repo (owner/name).

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

Input Schema

NameRequiredDescriptionDefault
nameYes
registryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.2

TDQS

B3.1/5.0
Behavior2/5

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

readOnlyHint=true already tells the agent this is a safe read, and the description adds almost nothing beyond that — it does not say that lookups hit external registries/network, whether results are live or cached, what happens when a package is not found, or whether any rate limits apply. With annotation coverage in place, the description still leaves the operational behavior essentially undisclosed.

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; the parentheticals are doing real work by mapping ecosystems and the owner/name format. The phrasing 'Current version and facts of a package ... or GitHub repo' is slightly compressed but not confusing.

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?

For a two-parameter read-only lookup with annotations covering safety, the definition is minimally adequate. However, with no output schema, the vague term 'facts' is never expanded, so an agent cannot anticipate what fields come back, and the optionality/default of registry is unstated.

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

Parameters4/5

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

Schema coverage is 0%, so the description must carry the parameter burden, and it does the important part: it enumerates the registry values implicitly (npm, pypi, crates, github) and specifies the expected format for GitHub targets as 'owner/name'. It does not say whether registry is optional or how it is auto-detected when omitted, which is the remaining ambiguity.

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 the resource (package or GitHub repo), the kind of data returned (current version and facts), and the supported ecosystems (npm, pypi, crates, github). That is enough to distinguish it from any sibling in the catalog, though the verb is implicit rather than stated (there is no 'fetch'/'retrieve').

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 alternatives such as deps_check, which could plausibly overlap. The agent must infer from the tool name alone that this is the lookup tool rather than a dependency analysis tool.

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