Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get npm package provenance

npm_package_provenance_get
Read-onlyIdempotent

Retrieve and decode the publish and SLSA provenance attestations attached to an npm package version from its sigstore bundles, helping verify how and where it was built.

Instructions

Get the publish and SLSA provenance attestations attached to an npm version, decoded from their sigstore bundles. 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_provenance_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.
includeNo`raw` also returns each sigstore bundle. Signatures are decoded, not verified.
versionNoExact version or dist-tag. A dist-tag is resolved to the version it points to. Default: `latest`.
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.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description adds real context beyond that: the data comes from sigstore bundles and is decoded rather than verified. It does not say what happens on a missing attestation (empty result vs error), which is the main remaining behavioral unknown.

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, front-loaded with the core action and the decoding detail. The trailing 'Requires `name`' is redundant with the schema's required array and is the only wasted clause.

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?

There is no output schema, so the description carries some burden for describing the return shape; it conveys only that attestations are decoded from sigstore bundles. For a read-only lookup this is mostly sufficient, but the absence of any statement about the no-attestations case leaves a meaningful hole for an agent deciding whether to call it.

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 name, version, include, context, llm_model and conversation_id are all documented in the schema itself, including the crucial 'signatures are decoded, not verified' note on `include`. The description only restates that `name` is required and adds nothing about `version` defaulting to latest or the raw-bundle option. Baseline 3 is appropriate when the schema does the heavy lifting.

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 names a specific verb and resource: fetching publish and SLSA provenance attestations for an npm version, decoded from sigstore bundles. That is far more specific than a generic 'get package info' and clearly distinguishes it from npm_package_version_get or npm_package_details_get. It stops short of naming a sibling or stating the contrast explicitly, 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?

Usage is implied by the resource: an agent would call this when it needs supply-chain/provenance evidence rather than metadata or download counts. There is no explicit when-to-use statement, no exclusion of alternatives, and no mention of what to do when a version has no attestations. Adequate but with clear gaps.

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