Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get npm package

npm_package_get
Read-onlyIdempotent

Retrieve an npm package's latest version, dist-tags, publisher, dependencies, and last week's downloads by name to evaluate a dependency.

Instructions

Get an npm package's latest version, every dist-tag, publisher, dependencies and last week's downloads. 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_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

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful context about what data is retrieved (including a time-bounded 'last week's downloads' snapshot), but says nothing about failure behavior for unknown packages, data freshness, or rate limits.

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 front-loaded sentence with the key scope (aggregate package info) first and the requirement last — no filler or repetition.

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?

With no output schema, the description correctly compensates by listing the returned fields, and annotations carry the read-only safety profile. It falls short only on edge cases (nonexistent or unpublished packages) and on clarifying how its aggregate output relates to the more granular sibling tools.

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 schema already documents `name` in depth (case sensitivity, legacy punctuation, examples) as well as the plumbing parameters `context`, `llm_model`, and `conversation_id`. The description's 'Requires `name`' merely restates the schema, so 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?

States a specific verb (Get) and resource (npm package) and enumerates exactly what is returned: latest version, every dist-tag, publisher, dependencies, and last week's downloads. That makes the tool's scope distinguishable from narrow siblings like npm_package_downloads_get or npm_package_versions_list, although the description never names those siblings to make the routing explicit.

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?

Usage is only implied: the aggregated field list suggests 'use this for a one-shot overview of a package' while more targeted siblings exist, but the description never states when to prefer this over npm_package_details_get or npm_package_downloads_get. No prerequisites or exclusions are given.

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