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

io.github.kushvinth/crowbar

cb_tables

Map every CVE and exploit index table to its contents and the command or dataset that feeds it, so agents can query the correct source for vulnerability intelligence.

Instructions

Data map: every index table, what it holds, and which command/dataset feeds it.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.5

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden, and it does convey that this returns reference metadata rather than data records. It does not state that the call is side-effect free, whether the map is static or reflects live state, or how large the response is — gaps that matter less for an intuitive zero-argument listing but are still unaddressed.

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 tight clause with the key noun front-loaded; every element (tables, contents, feeder command) carries information. It is a sentence fragment rather than a full sentence, but nothing is wasted or buried.

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 zero-parameter, no-output-schema tool the description supplies what the agent needs: the scope (all index tables) and the shape of each entry (contents plus the command/dataset that feeds it). Detail on return format or navigation advice is absent, but the definition is adequate to decide whether to call it.

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 no schema semantics for the description to add; the baseline for a zero-param definition applies. Nothing in the description conflicts with the empty object 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?

"Data map: every index table, what it holds, and which command/dataset feeds it" names a specific resource (index tables) and enumerates the three things returned, so an agent knows this is a catalog/inventory tool rather than a query tool. The verb is elided behind the noun phrase "Data map", and there is no explicit contrast with siblings like cb_search or cb_sql, which keeps it 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 Guidelines3/5

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

Usage is only implied: by saying it maps tables to the command/dataset that feeds them, the description hints this is a discovery/orientation step preceding the cb_* query tools. It never states when to call it, when not to, or names any alternative, so the agent must infer the routing role itself.

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