Skip to main content
Glama

MCP Tool-Poisoning, Prompt-Injection & 2026 EU AI Act Auditor MCP

Batch Audit Up to 15 SBOM Dependencies ($0.006 USDC via x402)

batch_sbom_cve_audit_x402
Read-onlyIdempotent

Audits up to 15 dependency specs in parallel against OSV.dev + CISA KEV ($0.006 USDC on Base via x402).

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

Input Schema

NameRequiredDescriptionDefault
packagesYesItems like npm:lodash@4.17.19

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, open-world semantics, and the description still adds genuinely new behavior: parallel execution, the two upstream sources, and a concrete paid-usage cost of $0.006 USDC on Base via x402. It omits failure/payment-settlement behavior and what happens to the batch when one spec is invalid.

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?

A single sentence that front-loads the capability, the batch limit, the data sources, and the price. No redundant restatement beyond the title's framing, and nothing extraneous.

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, and the description says nothing about what the audit returns (per-package verdicts, CVE lists, KEV flags) or how payment failure is surfaced, which matters for a paid tool. For a one-parameter tool with full schema coverage this is workable but leaves the agent guessing about results and error paths.

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% and the schema already shows the 'npm:lodash@4.17.19' item format. The description contributes one thing the schema does not encode: the array is capped at 15 items, which is a real constraint on the packages parameter.

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 (audits) and resource (dependency specs / SBOM entries) plus the data sources (OSV.dev and CISA KEV), and the 'batch up to 15' framing implicitly separates it from the single-package sibling audit_package_cve_and_cisa_kev. It never names that alternative, so differentiation requires an inference.

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 'up to 15' cap and 'in parallel' phrasing imply this is the bulk path rather than the per-package one, but there is no explicit when-to-use statement, no guidance for a single package, and no mention of what to do if the list exceeds 15 entries.

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.