Skip to main content
Glama

npm_get_package

Read-onlyIdempotent

Retrieve metadata and version information for an npm package by name, enabling you to inspect package details before installing or using it.

Instructions

Get metadata for an npm package (latest 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": {
      "name": "<name>"
    },
    "name": "npm_get_package"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesPackage name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

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, non-destructive and openWorld, so safety is well covered. The description adds one useful behavioral fact beyond that: it returns latest-version metadata only, not version history. It says nothing about response shape, rate limits, or behavior for missing/private/unpublished packages.

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 short sentence with the resource and the version qualifier front-loaded; nothing redundant or padded.

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 one-parameter read tool with rich annotations this is close to adequate, but with no output schema the agent is left guessing what 'metadata' contains (dependencies, dist-tags, publish date, tarball URL). A brief field list would close the gap.

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?

One parameter at 100% schema coverage, so the schema already documents 'name'. The description adds no naming syntax (scope prefixes like @scope/pkg, case sensitivity) beyond the schema, which is the baseline-3 case.

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?

States a specific verb (Get) and resource (metadata for an npm package) with a clear scope qualifier, '(latest version)'. It is distinguishable from npm_search, but never names that sibling to reinforce the split.

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?

The 'latest version' qualifier implies this is for looking up one known package rather than browsing, but there is no explicit 'use npm_search to find a package name first' guidance or any exclusion. Usage is inferable, not stated.

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

Deploy Server

Other Tools