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

io.github.kushvinth/crowbar

cb_kev

Queries the CISA Known Exploited Vulnerabilities catalog by keyword and returns limited results, helping agents identify actively exploited CVEs.

Instructions

CISA Known Exploited Vulnerabilities catalog.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "cb_kev"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.5

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, yet it only names the dataset. It says nothing about read-only semantics (implied only weakly by 'catalog'), pagination, result ordering, or what happens with an empty query. This is a significant gap for a tool with zero structured behavioral metadata.

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?

One short sentence fragment with no wasted words, so it is concise and front-loaded. However, the brevity comes from under-specification rather than discipline, and there is no structure telling the agent what the call does or returns.

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?

With no annotations, no output schema, and no parameter documentation, the description is the only source of context and supplies just a dataset label. For a two-parameter search tool, an agent still lacks enough to call it confidently or predict its results.

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% with two parameters, so the description must compensate and does not. It never mentions what 'query' matches (vendor, product, CVE ID, free text) or that 'limit' caps result count at 200 with a default of 25 — leaving the agent to guess at matching semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description expands the 'kev' acronym into 'CISA Known Exploited Vulnerabilities catalog', which does identify the resource. But it is a bare noun phrase with no verb, so the agent cannot tell whether the tool lists, searches, or fetches entries — and the presence of 'query' and 'limit' parameters is the only hint that it is a searchable lookup.

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 rather than siblings such as cb_cve, cb_exploit, or cb_poc, all of which plausibly overlap on vulnerability data. No prerequisites or exclusions are stated; the agent must infer usage from the dataset name alone.

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