Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get npm package full registry document

npm_package_details_get
Read-onlyIdempotent

Fetch an npm package's full registry document, including every version, README, star count, and timestamps, by passing the package name.

Instructions

Get npm package registry document with every version, README, stars and timestamps. Requires name.

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": {
      "name": "<name>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "npm_package_details_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesRequired. npm package name, e.g. `express`, `lodash.merge`, `@types/node` or `--file--1`. Names are case-sensitive (`Express` is a different package) and keep legacy punctuation such as a leading `-`.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered by structured data. The description adds real value by disclosing the payload shape (all versions, README, stars, timestamps), which implies a large response, but it does not warn about response size, truncation, rate limits, or unpublished/deprecated package behavior.

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?

Two short sentences with the capability front-loaded and the requirement trailing. Nothing is padded, but the second sentence is largely redundant with the schema and could have been replaced by more informative content such as expected payload size.

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?

With no output schema, the description should carry more of the return-value burden; it names the fields but not the structure, size, or whether README content is truncated. For a read-only fetch whose annotations already cover safety, this is adequate but leaves an agent guessing about response volume and shape.

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%, and the `name` parameter already documents case sensitivity, scoped names, maxLength and legacy punctuation in detail. The description's only parameter statement, 'Requires `name`', restates the schema's required list and adds nothing, 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 states a specific verb and resource: fetch the npm registry document, and enumerates its contents (every version, README, stars, timestamps). That is enough for an agent to know this is the full-document fetch rather than a narrow lookup, though it never explicitly distinguishes itself from close siblings like npm_package_get or npm_package_versions_list.

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?

There is no when-to-use guidance, no when-not-to-use, and no reference to any alternative tool. The only conditional statement is 'Requires `name`', which is a requirement restatement rather than routing advice. An agent must infer from the name alone when to pick this over the sibling package tools.

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