Skip to main content
Glama

npm_search

Search the public npm registry for packages to support supply-chain and dependency research, returning versions, publishers, keywords, links, and registry scores.

Instructions

Search the public npm registry for packages (keyless).

Returns name, latest version, description, publisher, date, keywords, links and the registry score. Useful for supply-chain and dependency research.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description does carry some burden and does add value: it discloses that no API key is required and enumerates the returned fields including registry score. However it is silent on rate limits, result ordering/relevance, and pagination behavior, which matter for a registry search tool.

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-loaded with the core action and free of filler. The return-field list is a little dense but each item is informative.

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?

For a simple two-parameter read-only lookup with no output schema, the description is nearly sufficient because it enumerates the response fields. The gap is the undocumented query/limit parameters, which the schema does not cover either.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate. It gives no meaning for `query` (search syntax? scoped packages? exact match?) and never mentions `limit` or its default of 10, leaving both parameters undocumented anywhere.

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?

States a specific verb and resource ("Search the public npm registry for packages"), which is distinct from the sibling search tools like github_search or web_search. The "keyless" qualifier also clarifies scope of access.

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?

Offers a use context ("supply-chain and dependency research") but never states when to prefer this over the many sibling search tools, nor any exclusions. Usage is implied rather than prescribed.

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