Skip to main content
Glama
offsec-mcp

offsec-mcp

by nadirzhon

Cve Lookup

cve_lookup

Fetch full details and references for a specific CVE ID to support vulnerability research, triage, and validation.

Instructions

Fetch full details and references for a specific CVE id (e.g. CVE-2024-3094).

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

Input Schema

NameRequiredDescriptionDefault
cve_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations, so the description carries the burden; 'Fetch' implies a read-only operation but authorization needs, rate limits, whether data is live from NVD or cached, and error behavior for an unknown ID are all unstated. It does add that the response contains 'full details and references', which is useful context beyond the name.

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 front-loaded sentence with no filler, and the example is embedded efficiently. It could be tightened only marginally.

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

Completeness3/5

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

An output schema exists and the tool has one simple required parameter, so little description is strictly needed. Still, for a lookup tool the agent has no information about failure modes or upstream source, which is a noticeable gap.

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 0% for the single cve_id parameter, but the inline example 'CVE-2024-3094' conveys the expected format, which is genuine added meaning. It does not address case sensitivity, normalization, or validation behavior on malformed IDs.

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 (Fetch) and resource (full details and references for a specific CVE id), which clearly separates it from a search-style operation. It does not explicitly name the sibling cve_search, so differentiation is inferred rather than asserted.

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?

Use is implied by 'specific CVE id', which contrasts with the list-oriented cve_search sibling, but the description never says when to prefer this over cve_search or what to do when the ID is unknown. No explicit exclusions or prerequisites are given.

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