Skip to main content
Glama

AutoTasker Hub — China Social Data API

npm_search

Search npm registry with download counts. Dev-tool finder. $0.01 USDC.

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 observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations exist, so the description carries the full behavioral burden and it discloses only one genuine trait: the $0.01 USDC cost, which is useful and non-obvious. It says nothing about what the search returns beyond "download counts" (sorting, ranking, popularity weighting), result volume relative to limit, or error behavior on empty queries. For a zero-annotation tool this is a thin disclosure, though the pricing note and the inherently read-only nature of search keep it above a 1.

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?

Three short fragments, front-loaded with the verb and resource, no filler sentences. Nothing is redundant, though the telegraphic style leaves no room for the schema-compensating detail this tool needs. Appropriate size, slightly under-written rather than over-written.

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

Completeness2/5

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

With no annotations, no output schema, and 0% parameter coverage, the description should be doing the heavy lifting and it is not. An agent still cannot tell how results are ranked or shaped, what download-count data looks like, or how the USDC charge is triggered (per call vs per result). The complexity is low, which keeps this from a 1, but the gaps are material.

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% across 2 parameters, so the description is responsible for compensating and it does not — 'query' (string) and 'limit' (integer, default 5, max 20) get no explanation of matching semantics, prefix vs substring behavior, or what limit caps. "With download counts" describes the response, not any input. The agent learns parameter meaning only from bare types in 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?

The phrase "Search npm registry with download counts" gives a specific verb (search) plus the exact resource (npm registry) and a hint of the result enrichment (download counts), which cleanly separates it from the sibling registry searches such as crates_search and pubmed_search. "Dev-tool finder" adds a light use-case gloss. It stops short of naming a sibling alternative, so it lands at 4 rather than 5.

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?

"Dev-tool finder" implies the context (finding developer tooling rather than, say, academic papers), which is the only usage signal present. There is no explicit when-not guidance, no mention of preferring another tool for package-to-package lookups, and no prerequisites. Usage must be inferred from the tagline, which is the definition of a 3.

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.