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

io.github.kushvinth/crowbar

cb_stats

Check local CVE index health and freshness: reports age, stale status beyond the 8-day NVD window, and last update error; run crowbar update when stale.

Instructions

Corpus health and freshness. index.age_days is days since the last update; index.stale means older than the 8-day NVD change window, so recent CVEs may be missing or outdated - say so and run crowbar update. index.last_error is why the last background update failed.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.5

TDQS

A4/5.0
Behavior4/5

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

With no annotations and no output schema, the description carries the full burden and does real work: it explains what staleness means (older than the 8-day NVD change window), the consequence (recent CVEs may be missing or outdated), and the meaning of the error field. It does not cover any fields beyond those three, so an agent still doesn't know the full response shape.

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?

Three tight sentences, front-loaded with the purpose and then moving field-by-field to consequences and the recommended action. No filler, though the backtick-dense phrasing makes it read more like a fragment list than prose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a no-parameter diagnostic tool with no output schema, the description supplies enough to interpret the key fields and act on them, including the follow-up command. It is incomplete only in that it documents three fields of what is presumably a larger stats object, leaving other returned keys unexplained.

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

Parameters4/5

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

The tool takes no parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description instead spends its space on return-value semantics, which is the right allocation for a zero-argument tool.

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?

"Corpus health and freshness" names the resource and the aspect reported, and the field names (`index.age_days`, `index.stale`, `index.last_error`) make clear this is a status/diagnostics tool rather than a lookup. It is clearly distinct from the data-query siblings like cb_cve or cb_search, though it never states explicitly that it reports on the local corpus index.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives conditional guidance: if `index.stale` is true, tell the user and run `crowbar update`. That is actionable remediation tied to a specific state. It stops short of saying when to call cb_stats in the first place (e.g., before relying on CVE data), so it is clear context but not full when/when-not routing.

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