Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get one npm package version

npm_package_version_get
Read-onlyIdempotent

Fetch one npm package version by exact version or dist-tag to retrieve its files, dependencies, scripts, and registry metadata for package and dependency analysis.

Instructions

Get one npm version document, by exact version or dist-tag, with its files, dependencies, scripts and registry metadata. Requires name and version.

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>",
      "version": "<version>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "npm_package_version_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.
versionYesRequired. Exact version or dist-tag, e.g. `5.3.0`, `5.0.0-alpha.1`, `latest` or `latest-4`. Semver ranges (`^4`, `4.x`) are refused.
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

A3.6/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 fully covered. The description adds useful payload context by enumerating what comes back (files, dependencies, scripts, registry metadata), but says nothing about failure modes (unknown version, refused semver range) or registry/rate-limit behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence with zero filler; the payload contents come first and the input requirement is front-loaded at the end. Nothing could be removed without losing information.

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 read-only lookup with a fully described schema and no output schema, the definition covers resource, selector form and returned content. The only mild gap is that the analytics/conversation meta-parameters are left entirely to the schema, which is acceptable since they are thoroughly documented there.

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%, so all five parameters including the meta-parameters are already documented in the schema. The description's only parameter statement, 'Requires `name` and `version`', restates required-field information rather than adding syntax or format meaning. Baseline 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 pairs a specific verb ('Get') with a precise resource ('one npm version document') and scope ('by exact version or dist-tag'), which clearly separates it from list-style siblings such as npm_package_versions_list. It stops short of naming an alternative tool explicitly, so it is clear but not fully sibling-differentiated.

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?

'By exact version or dist-tag' implies the selection condition, and the requirement of `name` and `version` is stated. However, there is no explicit when-to-use versus a sibling (e.g. details_get or versions_list), and no when-not guidance beyond the version-format constraint that already lives in the schema.

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