Skip to main content
Glama

Advisories for packages

get_advisories
Read-onlyIdempotent

Check npm packages for security advisories. Start here before installing, upgrading or deploying: send 1 to 50 package names (never versions) and get, per package, its total and up to 20 advisories of the last 120 days, newest first, each with vulnerable ranges, fixed versions and the conditions that make it exploitable. A package with none returns total 0. Compare the ranges with your lockfile. For a daily check, pass since (the time of your last check) to get only what is new. For one advisory in full use get_advisory; for the version to upgrade to, use latest_safe.

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": {
      "packages": "<packages>"
    },
    "name": "get_advisories"
  }
}

Input Schema

NameRequiredDescriptionDefault
sinceNoOnly advisories new since this ISO date or date-time ("2026-10-27" is UTC midnight, or "2026-10-27T08:00:00Z"): published, or first read by Patchwire, after it. For a daily check, pass the time of your last check. Omit for the last 120 days.
packagesYesnpm package names as written in package.json, 1 to 50, for example ["next", "@supabase/supabase-js"]. Names only, never versions: compare the returned ranges with your lockfile.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / since
      Added value: +{
      +  "description": "Only advisories new since this ISO date or date-time (\"2026-10-27\" is UTC midnight, or \"2026-10-27T08:00:00Z\"): published, or first read by Patchwire, after it. For a daily check, pass the time of your last check. Omit for the last 120 days.",
      +  "pattern": "^\\d{4}-\\d{2}-\\d{2}(T\\d{2}:\\d{2}(:\\d{2}(\\.\\d{1,3})?)?(Z|[+-]\\d{2}:\\d{2}))?$",
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • addedInput schema / properties / packages / description
      Added value: +"npm package names as written in package.json, 1 to 50, for example [\"next\", \"@supabase/supabase-js\"]. Names only, never versions: compare the returned ranges with your lockfile."
  3. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds substantial context beyond them: per-package total plus up to 20 advisories from the last 120 days, newest first, with vulnerable ranges, fixed versions and exploitability conditions, plus the zero-result convention (total 0). That is the return-shape disclosure an agent needs, since there is no output schema.

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?

Front-loaded with the core action and the routing advice, and every sentence carries operational content. However, 'never versions' and the lockfile comparison are stated twice (in the description body and again in parameter text), which is mild redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, yet the description fully specifies the return shape, ordering, window, zero-result behavior and actionable follow-up. Combined with the annotations, nothing an agent needs in order to invoke this correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds workflow meaning the schema lacks: names only and never versions, and the instruction to compare returned ranges with the lockfile, plus propagating since as 'the time of your last check' for incremental polling. Slight duplication of the schema text keeps it off a 5.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Check npm packages for security advisories', and immediately differentiates itself from get_advisory (single advisory) and latest_safe (upgrade target). An agent can place it among its siblings without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit when-to-use ('before installing, upgrading or deploying') and names both alternatives with the condition that selects each: get_advisory for one advisory in full, latest_safe for the upgrade version. It also documents the daily-check pattern via the since parameter.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources