Skip to main content
Glama
io.github.kushvinth/crowbar

io.github.kushvinth/crowbar

cb_cve

Retrieve complete CVE intelligence—CVSS, EPSS, KEV, CWE, CPE ranges, references, exploit hits, and SSVC decisions—to assess vulnerability risk and prioritize remediation.

Instructions

One CVE in full: CVSS, EPSS, KEV, CWE, CPE version ranges, references, Exploit-DB / Nuclei / Metasploit hits, SSVC decision points.

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

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.5

TDQS

B3/5.0
Behavior3/5

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

No annotations exist, so the description carries the full behavioral burden. It does useful work by disclosing the returned payload sections in lieu of an output schema, but it says nothing about lookup behavior: what happens for a malformed or unknown CVE ID, whether missing enrichment degrades gracefully, or auth/rate-limit requirements.

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?

A single tight sentence, front-loaded with the core scope ('One CVE in full') followed by the enrichment list. The telegraphic enumeration is dense but every item conveys payload content rather than filler.

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?

For a one-parameter lookup tool with no output schema and no annotations, the description adequately covers what data comes back, which is the main uncertainty. It leaves gaps on ID format and error/not-found behavior that matter for correct invocation.

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

Parameters2/5

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

Schema description coverage is 0% and the single required parameter 'id' is completely undocumented. The description never indicates the expected identifier form (e.g. CVE-YYYY-NNNN) versus a bare number or alias, so an agent has no basis for constructing a valid value beyond guessing.

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 resource (a single CVE) and its scope ('in full'), then enumerates the enrichment sections returned (CVSS, EPSS, KEV, CWE, CPE ranges, references, exploit hits, SSVC), which distinguishes it from narrower siblings like cb_kev or cb_cwe. It never states the operative verb ('retrieve/lookup') explicitly, but the intent is unambiguous.

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 when-to-use guidance, no prerequisites, and no routing to alternatives such as cb_kev for browsing the KEV catalog or cb_search for finding CVEs. The phrase 'in full' faintly implies this is the deep-detail lookup versus partial views, but the agent must infer that entirely.

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