Skip to main content
Glama

UAI x402 Security Tools

cve-lookup

CVE lookup and vulnerability search — resolve a CVE ID via OSV and return summary, severity, affected packages, and references for agent triage. (REST equivalent: POST /api/v1/cve-lookup, $0.01)

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

Input Schema

NameRequiredDescriptionDefault
cveIdYesCVE identifier (CVE-2021-44228)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations supply only a title, so the description carries the burden and does add real value: it discloses the upstream data source (OSV), the returned fields, the REST equivalent endpoint, and a $0.01 cost. It does not mention rate limits, failure behavior for unknown CVE IDs, or caching, which keeps it below a 5.

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 plus a parenthetical for endpoint and price — front-loaded and nearly waste-free. The only cost is the 'vulnerability search' framing, which pads the purpose without matching the actual input.

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 single-parameter read tool with no output schema, the description covers what it does, where data comes from, what comes back, and what it costs. Enough for correct invocation; only error/edge behavior is 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 coverage is 100% and the schema already documents cveId with a concrete example (CVE-2021-44228). The description adds no format constraints, version handling, or validation rules beyond what the schema provides, so this sits at the baseline.

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 and resource ('resolve a CVE ID via OSV') and enumerates the returned fields, which is far more than a restatement of the name. However, the opening phrase 'vulnerability search' is slightly misleading since the schema accepts only a single cveId and no search term, and no sibling (e.g. dependency-cve-scan) is named to delineate single-CVE lookup from scanning.

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?

'for agent triage' hints at the intended context, and requiring a CVE ID implies use only when an identifier is already known. There is no explicit when-not guidance and no named alternative for the neighboring scanning tools, so routing is left to inference.

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