Skip to main content
Glama

Antigravity x402 & MCP Gateway

check_cisa_kev_exploits

[0.004000 USDC via x402] Checks any CVE identifier or vendor/product keyword against the live CISA Known Exploited Vulnerabilities (KEV) catalog, returning active exploitation status, ransomware usage, due dates, and CWEs.

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": {
      "query": "<query>"
    },
    "name": "check_cisa_kev_exploits"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum matching KEV entries to return (1 to 15, default 5).
queryYesExact CVE ID (e.g., 'CVE-2024-21762') or vendor/product keyword (e.g., 'Fortinet', 'Ivanti').
x402_payment_signatureNoOptional base64 x402 PAYMENT-SIGNATURE header token (0.004000 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, the description carries the full burden and does reasonably well: it discloses that the catalog is live, that it returns exploitation status, ransomware usage, due dates and CWEs, and it front-loads the paid x402 model and price. It stops short of stating that a miss means the CVE is absent from KEV (as opposed to not exploited), or any rate/limit 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?

One dense sentence preceded by a short price tag — the resource and output fields are front-loaded with no filler. The bracketed payment prefix is slightly awkward but conveys a genuinely useful constraint before the agent commits.

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 three-parameter lookup with no output schema, the description usefully previews the response fields, which compensates for the missing output schema. Combined with the fully documented input schema, an agent has enough to call it correctly; only the semantics of an empty result are unaddressed.

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 all three parameters (query, limit, x402_payment_signature) are already documented with examples and defaults. The description restates the query forms but adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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?

The description states a specific verb ('Checks') and resource ('live CISA Known Exploited Vulnerabilities (KEV) catalog'), and enumerates the returned fields (exploitation status, ransomware usage, due dates, CWEs). An agent can tell exactly what this tool does without opening the schema, and no sibling covers CVE/KEV lookups.

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?

It implies usage by naming accepted query forms (exact CVE ID or vendor/product keyword), which tells an agent when the tool applies. However, there is no explicit when-not guidance, no mention of coverage boundaries (e.g., non-KEV CVEs will return nothing), and the payment flow guidance lives in the schema rather than the description.

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.