Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_cve_lookup

Read-onlyIdempotent

Retrieves CVE records from NVD by CVE ID, enabling analysts to verify vulnerability details without inventing intelligence.

Instructions

Retrieve a CVE record from NVD without inventing intelligence.

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_id": "<cve_id>"
    },
    "name": "oc_cve_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
cve_idYes
timeoutNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered elsewhere. The description adds only the vague admonition "without inventing intelligence," which hints at a grounding/strictness constraint but never specifies what happens on unknown CVE IDs, whether errors are raised, or whether results are cached or live-fetched from NVD.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short sentence, which is appropriately front-loaded, but the trailing clause is rhetorical rather than informative and displaces content that would actually help an agent call the tool correctly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained, but for a two-parameter tool with zero schema descriptions the definition should at minimum explain the CVE ID format and timeout behavior. As written, key calling details are undocumented anywhere.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the description does nothing to compensate: it never states the expected cve_id format (e.g., CVE-YYYY-NNNN) or what units/semantics the optional timeout has. For a tool whose only meaningful input is an identifier with strict formatting, this is a real usability hole.

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?

The description names a specific verb and resource ("Retrieve a CVE record") plus the authoritative source (NVD), which is more specific than the name alone. It does not differentiate from any sibling, but no sibling in the list appears to overlap, so the gap is minor.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus alternatives (e.g., a local vulnerability DB or advisory search), no prerequisites, and no indication of when a lookup would fail or be inappropriate. The agent must infer all usage context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools