Skip to main content
Glama

Paid public-data feeds (x402, 0.002 USD)

npm package facts in one call: latest version, description, license, dependency count, repository, weekly downloads (nam

npm_package
Read-onlyIdempotent

npm package facts in one call: latest version, description, license, dependency count, repository, weekly downloads (name=express). For dependency and supply-chain agents. Pay per call $0.002 USDC on Base via x402.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "npm_package"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNopackage name, e.g. express or @scope/pkg
x_paymentNosigned x402 payment (X-PAYMENT header value); omit on the first call to receive the price and payment requirements

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare it is read-only, idempotent, open-world and non-destructive. The description adds genuinely new behavioral context the annotations cannot convey: it is a paid call at $0.002 USDC on Base via x402, which tells the agent to expect a payment handshake. It does not describe rate limits or failure behavior, keeping it short of a 5.

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?

Front-loads the resource and the returned fields in one dense clause, then appends audience and pricing. No filler sentences, though the comma-separated field list and parenthetical example make it read as a run-on title more than a structured description.

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?

With no output schema, the description usefully enumerates the key return fields so the agent knows what it gets for its money, and the pricing note covers the main non-obvious cost. Nothing critical is missing for a two-parameter read tool, though the multi-call payment flow is left entirely to the schema.

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 100%, including the scoped-package format and the x_payment handshake, so the schema carries the semantics. The description only restates the name example (name=express), adding nothing beyond 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 the resource (npm package) and enumerates exactly what is returned in one call (latest version, description, license, dependency count, repository, weekly downloads), which is more specific than a generic 'get package info'. The npm framing implicitly separates it from the pypi_package sibling, but there is no explicit differentiation statement.

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?

States the intended audience ('For dependency and supply-chain agents'), which implies usage context. It never says when to prefer this over a sibling like pypi_package or when it is inappropriate, so guidance is only implied.

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