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

io.github.kushvinth/crowbar

cb_new

Lists CISA KEV and ENISA exploited additions, recent CVEs, and new public PoCs since a date (default 7 days) so you can track vulnerability changes.

Instructions

What changed since a date (default 7 days): CISA KEV and ENISA exploited additions, newly published CVEs (KEV > EPSS > CVSS first), new public PoCs. Each part has total and the top rows.

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_new"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo
limitNo
sinceNoYYYY-MM-DD

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.5

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose meaningful behavior: the 7-day default window, the ranking rule for CVEs (KEV > EPSS > CVSS), and the response shape ("each part has total and the top rows"). What it omits is whether the tool is strictly read-only, pagination/truncation behavior when limit is small, and how the three parts are keyed in the response.

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 dense sentence group, front-loaded with the core question the tool answers, followed by the category list and the return-shape note. No filler, though the parenthetical ranking and the backtick-quoted field names make it read more like a spec fragment than prose.

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 three-parameter aggregation tool with no output schema, disclosing the top-level response shape is a genuine plus. Still missing are the `since`/`days` precedence rule and any routing guidance to the more granular sibling tools, which an agent would need to pick this tool confidently.

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 description coverage is only 33% — only `since` is documented in the schema. The description partially compensates by restating the 7-day default for `days` and by implying that `limit` controls the "top rows" per part, but it never clarifies how `since` overrides or combines with `days`, nor whether `limit` applies per part or to the whole result.

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 states a specific resource and time-scoped operation ("what changed since a date") and enumerates the three content categories it returns: KEV/ENISA additions, newly published CVEs, and new public PoCs. That is enough for an agent to distinguish it from single-source siblings like cb_kev or cb_poc, though it never names an alternative 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?

Usage is only implied: the agent can infer this is the "what's new" digest tool from the phrase "what changed since a date." There is no explicit when-to-use versus cb_kev/cb_cve/cb_poc, and no statement of when this aggregation is preferable to querying a single source.

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