Skip to main content
Glama

apex-dev

Cve lookup

cve_lookup
Read-onlyIdempotent

CVE vulnerability lookup by CVE ID or keyword combining official NVD 2.0, OSV.dev affected package versions, and CISA Known Exploited Vulnerabilities (KEV). $0.001 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for terms, then call again with payment.

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

Input Schema

NameRequiredDescriptionDefault
qNoKeyword search query (e.g. openssl). Pass q OR cve.
cveNoExact CVE ID (e.g. CVE-2021-44228). Pass cve OR q.
limitNoOptional max results for keyword search (1-20, default 5).
paymentNosigned x402 payment payload (PAYMENT-SIGNATURE).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations, the description discloses important behavior: it combines three external vulnerability sources, costs $0.001 per call via x402, supports specific chains/tokens, and requires a two-step no-payment terms call followed by a paid call. These are exactly the operational details an agent needs before invoking a paid lookup.

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?

The description is front-loaded with purpose, then cost, then call flow. Every sentence carries operational value, and the payment details are dense but necessary for correct invocation.

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 multi-source lookup with payment gating, the description covers the sources, cost, and two-call payment flow well enough to invoke correctly. It does not describe the return shape, which would have been useful since there is no output schema, but the core call requirements are complete.

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%, so the field definitions already carry most parameter meaning. The description adds useful semantics beyond the schema by explaining the `payment` lifecycle and by reinforcing the CVE-ID-versus-keyword input mode.

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 and resource: CVE vulnerability lookup by CVE ID or keyword. It also names the exact upstream sources (NVD 2.0, OSV.dev, CISA KEV), so an agent can tell this is a vulnerability-intelligence lookup rather than a generic search.

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?

The description gives a clear procedural guideline: call once without `payment` for terms, then call again with `payment`. It does not explicitly name when-not-to-use cases or alternatives, but the lookup context and payment prerequisite are sufficiently clear.

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