Skip to main content
Glama
Sign In
pkg-peep

pkg-peep

by chris-trag
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get_npm_package_info

Retrieve full NPM package metadata, including dependencies, versions, and repository info, to support package evaluation.

Instructions

Get comprehensive NPM package metadata

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

Input Schema

NameRequiredDescriptionDefault
packageYesNPM package name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full burden but only says 'comprehensive metadata' without detailing what fields are returned, whether network calls are made, or any limitations. The behavior is not transparent beyond the core purpose.

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?

The description is a single, concise sentence that is front-loaded with the action and resource. Every word contributes to defining the tool's purpose with no wasteful or redundant content.

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 with one well-defined parameter, but the term 'comprehensive' is vague and does not clarify expected output or edge cases. It is minimally sufficient but leaves the agent guessing about what metadata is actually included.

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% for the single 'package' parameter, which is already described as 'NPM package name'. The description adds no extra semantic meaning beyond restating the resource, so the baseline of 3 applies.

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 clearly states the tool fetches comprehensive NPM package metadata, with a specific verb and resource. It does not explicitly distinguish itself from get_npm_downloads, though the scope of 'comprehensive metadata' implies broader info than just downloads.

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?

No guidance is provided on when to use this tool versus the sibling get_npm_downloads. The description only states the basic action, leaving the choice of tool to inference from names.

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