Skip to main content
Glama

Search npm, crates, Packagist, RubyGems and NuGet packages

package_search
Read-only

Searches package names and descriptions on npm, crates.io, Packagist, RubyGems and NuGet, returning name, version, description, downloads where the registry gives them, licence, repository and last publish date. PyPI has no search API: it is checked by exact name only. Registries that fail are listed in unavailable. Limit per registry max 10. Related tools on this server, for a different need: package when you need facts about a package on npm, PyPI or crates.io: latest. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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

Input Schema

NameRequiredDescriptionDefault
qYesPackage name or keywords (1-100 characters)
limitNoResults per registry, 1-10 (default 5)
ecosystemsNoComma list of npm, crates, packagist, rubygems, nuget, pypi (default: all)

Output Schema

NameRequiredDescriptionDefault
countNo
queryNo
sourceNo
resultsNo
pypiNoteNo
checkedAtNo
unavailableNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare readOnly and openWorld, so the description carries real additional weight: what fields come back ("downloads where the registry gives them, licence, repository and last publish date"), partial-failure behavior ("Registries that fail are listed in unavailable"), a PyPI coverage caveat, and per-call pricing with the explicit note that failed calls are not charged.

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?

It is front-loaded with purpose and return shape, then limitations, then economics — a sensible order with little waste. The final pricing sentence is long and dense, and the sibling-routing clause is awkwardly punctuated, but every sentence still carries information an agent needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists and annotations cover the safety profile, so the description need not explain return values in detail — yet it summarizes them, documents the registries, states the failure mode, and discloses cost. For a three-parameter, multi-registry search tool this leaves no material gap.

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 100%, so the baseline is 3, but the description adds meaning the schema does not: "Limit per registry max 10" clarifies that limit applies per registry rather than in aggregate, and the PyPI exact-name-only rule changes how an agent should treat pypi in the `ecosystems` list.

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?

The description states a specific verb and resource ("Searches package names and descriptions") and enumerates the exact registries covered, then lists the return fields. It also distinguishes itself from the `package` sibling, so an agent can route without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly names the alternative ("package when you need facts about a package on npm, PyPI or crates.io: latest") and the condition that selects it, plus a key constraint that PyPI is exact-name only. The routing sentence is slightly garbled in phrasing, which keeps this just below a 5.

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