Skip to main content
Glama

Patchfirst

Check stack

check_stack
Read-onlyIdempotent

Check a list of packages for known vulnerabilities via OSV.dev, then join with Patchfirst exploitation data (CISA KEV, EPSS, priority, ATT&CK techniques). Results are sorted exploited-first so you fix what attackers actually use. Ecosystems use OSV names: npm, PyPI, Maven, Go, crates.io, RubyGems, NuGet, Packagist, Debian, Alpine, etc.

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": "check_stack"
  }
}

Input Schema

NameRequiredDescriptionDefault
packagesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive and open-world, so the bar is lower; the description still adds real context: the upstream dependency on OSV.dev, the enrichment sources joined in, and the exploited-first result ordering that shapes interpretation of output. No output schema exists and the description does not sketch the response shape, which keeps it from a 5.

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?

Three tight sentences, front-loaded with what it does, then why the ordering matters, then the ecosystem vocabulary. Every sentence carries information an agent needs and none repeats structured fields.

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, single-parameter batch scanner with no output schema, the definition covers purpose, sources, result ordering, and ecosystem naming well. Minor gaps: the 100-package limit and likely per-package failure behavior are left to the schema or unstated.

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?

Top-level schema coverage is 0% (the packages array itself is undocumented), but the description compensates meaningfully by enumerating valid OSV ecosystem identifiers (npm, PyPI, Maven, Go, crates.io, ...) which the schema does not provide as an enum. It does not cover the 100-package cap or the name-format convention for Maven coordinates beyond the schema's own example.

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 and resource ('check a list of packages for known vulnerabilities') plus the enrichment pipeline and data source (OSV.dev, CISA KEV, EPSS, ATT&CK). It is clearly distinguishable from get_vulnerability and cves_for_technique by being a batch package-to-vuln lookup, though it never names a sibling to route away from.

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 sorted exploited-first rationale tells the agent why to call it for triage, but there is no explicit when-to-use versus get_vulnerability/search, and no stated exclusions or prerequisites.

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