Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List npm package security advisories

npm_package_advisories_list
Read-onlyIdempotent

Lists security advisories for a specific npm package version or all versions, helping users identify known vulnerabilities before installing or upgrading dependencies.

Instructions

List the security advisories affecting an npm package version, or every version. Requires name. Returns a list.

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_advisories_list"
  }
}

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.
versionNoExact version or dist-tag to check, `all` for every version, or omit for `latest`. A dist-tag is resolved to the version it points to. Semver ranges are not resolved.
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
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description itself adds almost nothing beyond that: "Requires `name`. Returns a list" restates schema facts and gives no detail on what an advisory record contains, ordering, or pagination 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 resource and scope front-loaded, so an agent gets the essentials immediately. The trailing "Returns a list" is low-value filler that does not earn its place.

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?

Annotations cover safety and the schema fully documents all five parameters, so the definition is callable as-is. However, with no output schema, the description's thin "Returns a list" leaves the shape of advisory results unexplained, which is a real gap for a data-retrieval tool.

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 every parameter is already documented in detail, and the rule sets the baseline at 3. The description repeats the `name` requirement without adding any semantics (e.g., version resolution or defaulting to `latest`) beyond 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 description gives a specific verb and resource ("List the security advisories affecting an npm package version, or every version") and clarifies the scope covers both a single version and all versions. This distinguishes it reasonably well from sibling detail/version tools, though it never names an alternative explicitly.

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?

The phrase "or every version" implies the `version: all` case, but there is no guidance on when to prefer this over siblings like npm_package_version_get or npm_package_details_get, nor any stated exclusions or prerequisites. Usage is only implied.

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