Skip to main content
Glama

Antigravity x402 & MCP Gateway

audit_package_supply_chain

[0.005000 USDC via x402] Audits 1 to 50 open-source dependencies across npm, PyPI, Crates.io, Go, and Maven against Google OSV.dev querybatch, enriches discovered CVEs with live FIRST.org EPSS 30-day exploitation probabilities and CISA Known Exploited Vulnerabilities (KEV) status, and returns minimum fixed versions plus a deterministic CI/CD release gate.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "audit_package_supply_chain"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoShorthand single-package name (e.g., 'lodash').
versionNoShorthand single-package version (e.g., '4.17.19').
packagesNoList of 1 to 50 package objects ({ecosystem, name, version}) to audit.
ecosystemNoShorthand single-package ecosystem ('npm', 'PyPI', 'Crates.io', 'Go', 'Maven').
x402_payment_signatureNoOptional base64 x402 PAYMENT-SIGNATURE header token (0.005000 USDC on Base eip155:8453 or Polygon eip155:137). Omit to receive the live x402 quote.

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?

With no annotations supplied, the description carries the full burden and does well: it discloses the 0.005000 USDC x402 cost, the batch size ceiling of 1-50, the external services queried, and that the response includes a deterministic release gate outcome. It stops short of describing failure modes, latency, or behavior on partial/unresolvable packages, and gives no explicit read-only assurance even though an audit is inherently non-mutating.

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?

A single dense sentence, but it is front-loaded with the price and then ordered logically: scope, sources, enrichment, return values. No filler or marketing language, though the multiple stacked clauses make it slightly harder to scan than a two-sentence split would be.

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 5-parameter, zero-annotation tool with no output schema, the definition covers cost, sources, batch limits, and the shape of the result, which is most of what an agent needs before calling. The remaining gap is that return-format detail and error behavior are unaddressed, which matters somewhat because no output schema exists to fill in.

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 the baseline is 3; the schema already documents name/version/ecosystem, the packages array, and the x402_payment_signature. The description restates the 1-50 bound and the ecosystem set but adds nothing about the relationship between the shorthand fields and the packages array (mutual exclusivity, precedence), which is the one ambiguity the schema leaves open.

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 ('Audits ... open-source dependencies') plus the exact upstream data sources (Google OSV.dev querybatch, FIRST.org EPSS, CISA KEV) and the output artifacts (minimum fixed versions, CI/CD release gate). An agent can tell this is a dependency-vulnerability auditor and not, for example, the sibling check_cisa_kev_exploits or evaluate_token_risk_verdict.

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 context is implied by the framing: use it to audit 1-50 dependencies across the five named ecosystems, and the description notes that omitting the payment signature yields a live x402 quote, which is a real operational hint. However, it never says when to prefer this over the related check_cisa_kev_exploits sibling, nor does it state exclusions or prerequisites (e.g., what happens with private/unpublished packages).

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.