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

io.github.kushvinth/crowbar

cb_product

Find CVEs affecting a product or vendor, and test a specific version against NVD CPE version ranges to identify matching vulnerabilities.

Instructions

CVEs affecting a product/vendor. Pass version to test NVD CPE version ranges, e.g. {name: nginx, version: 1.18.0}.

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

Input Schema

NameRequiredDescriptionDefault
nameYes
limitNo
versionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.5

TDQS

A3.5/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 burden. It usefully discloses the non-obvious behavior that supplying a version triggers NVD CPE version-range matching, but it says nothing about result ordering, pagination, truncation at the limit, or that this is a pure read operation.

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?

Two short sentences, front-loaded with the resource, then the key optional-parameter behavior with a compact example. Nothing is wasted.

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 simple three-parameter lookup with no output schema, the definition covers the main query shape but leaves the limit parameter and the shape of returned CVE records unaddressed, which matters since nothing else documents them.

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%, so the description must compensate. It explains 'name' as product/vendor and clarifies 'version' with a concrete example object, but the 'limit' parameter (default 25, max 200) is left entirely to the schema, which supplies no description at all.

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 and scope: 'CVEs affecting a product/vendor'. That is enough to distinguish it from an ID-based lookup like cb_cve, though no sibling is named explicitly.

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?

It gives a conditional usage cue for the optional parameter ('Pass version to test NVD CPE version ranges'), which implies the two modes of use. It never states when to prefer this over cb_cve, cb_advisory, or cb_kev, so routing still requires inference.

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