Skip to main content
Glama

Agent Data Tools: Full list (every tool as its own definition)

CVE lookup: severity, known exploitation, EPSS and fixes for a vulnerability

cve
Read-only

Look up a CVE by its ID: what the vulnerability is, its CVSS score and severity, whether CISA lists it as exploited in the wild (KEV) and since when, the EPSS probability of exploitation in the next 30 days, CISA's SSVC points, the weakness (CWE), affected products with fixed versions, and patch and advisory links. Use to triage a security alert, rank what to patch first, or check an advisory before upgrading a dependency. Example: cve=CVE-2021-44228. Price $0.002/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

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

Input Schema

NameRequiredDescriptionDefault
cveYesCVE ID such as CVE-2021-44228 (any case; a cve.org or nvd.nist.gov link works too)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description confirms it 'changes nothing' while adding value beyond them: billing is per call at $0.002 via x402 USDC or a card key, the first 25 are free, and failed calls are free. The line 'each call is charged, so repeats are not free' explains the practical meaning of idempotentHint=false in a way the annotation alone does not. Naming CISA/NVD-derived data also signals the open-world, externally sourced nature of the result.

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 resource, then the return payload, then usage contexts, then pricing, then the read-only reassurance. Each sentence carries information, though the pricing clause is dense ('$0.002/call via x402 USDC or a card key (/credits), first 25 free; failed calls free') and could be split for scannability.

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?

There is no output schema, so the description must describe return values — and it does so comprehensively by listing every returned data category. The only gap is structural: with no output schema, nothing conveys the response shape or field names, so an agent must call blind to learn the exact payload.

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?

With a single parameter at 100% schema description coverage, the schema already documents the ID format, case insensitivity, and URL acceptance. The description reinforces the ID-based lookup and gives an example value, but adds no format or validation detail beyond the schema. Baseline 3 applies.

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 precise verb+resource ('Look up a CVE by its ID') and then enumerates the exact payload: CVSS score/severity, KEV status and date, EPSS 30-day probability, SSVC points, CWE, affected products with fixed versions, and patch/advisory links. That is far more specific than a name restatement. It does not, however, differentiate itself from the sibling 'cve_lookup', which appears to cover the same resource.

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

Usage Guidelines4/5

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

Gives three concrete selection contexts: triaging a security alert, ranking patch priority, and checking an advisory before a dependency upgrade. It also provides a worked example (cve=CVE-2021-44228). No explicit when-not-to-use case or named alternative is given, so it stops short of a 5.

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.