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

io.github.kushvinth/crowbar

cb_trending

Identify actively discussed CVEs across security sources, ranked by distinct mentions, with KEV, EPSS, and CVSS context for prioritization.

Instructions

CVEs people are posting about right now, ranked by how many distinct places name them (Hacker News, oss-security, Full Disclosure, ZDI, Mastodon, ENISA EUVD exploited) with KEV/EPSS/CVSS beside each.

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

Input Schema

NameRequiredDescriptionDefault
daysNo
limitNo

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 are provided, so the description carries the full behavioral burden. It usefully discloses the ranking signal (count of distinct places naming a CVE) and the enrichment columns (KEV/EPSS/CVSS), which is genuine context. However it never states that this is a read-only operation, what happens when the limit truncates the ranking, how ties are broken, or what the result set looks like.

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 with the core concept (ranked CVEs) front-loaded and the parenthetical source list as supporting detail. Nothing is redundant, though the parenthetical makes it slightly crammed.

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?

With no annotations, no output schema, and 0% schema description coverage, the definition gives a good sense of what the tool is but not how to drive it. An agent knows why to call it yet must guess the effect of days and limit, which is a meaningful gap for a two-parameter tool.

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%, so the description must explain the two parameters and does not. 'Right now' loosely gestures at the days window but never states that days controls the lookback period or that limit caps the number of ranked CVEs returned. Both parameters, including their defaults and bounds, are left to the raw schema.

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 (CVEs) and a specific selection/ranking mechanism: frequency across distinct named sources (Hacker News, oss-security, Full Disclosure, ZDI, Mastodon, ENISA EUVD exploited). That is far more concrete than a generic 'get trending'. It does not explicitly contrast itself with siblings like cb_new or cb_kev, so it stops short of a 5.

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 explicit when-to-use or when-not-to-use guidance and no named alternative such as cb_new or cb_kev. 'People are posting about right now' hints at a recency/discovery use case, but the agent must infer it rather than being told.

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