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

io.github.kushvinth/crowbar

cb_exploit

Search an offline Exploit-DB index of 46,000 entries for exploits matching a keyword query. Returns matching records only; nothing is executed.

Instructions

Search the Exploit-DB index (46k entries), offline. To download the source for a numeric id, use the CLI: crowbar exploit <id>. Nothing is executed.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "cb_exploit"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.5

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It does add meaningful context beyond the structured fields: the search is offline against a local index, nothing is executed, and source retrieval requires a separate CLI step. However, it says nothing about what matching means (title, tags, CVE references), how results are ordered, or what the response contains.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with what the tool does, followed by the alternative path and the safety note. Every sentence earns its place and there is no filler.

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 two-parameter search tool with no output schema and no annotations, this is adequate but thin. The safety and offline context are well covered, but an agent still lacks search-field semantics and any sense of result shape or size, which the missing schema descriptions leave entirely undocumented.

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 compensate for both parameters and it largely does not. 'query' is only implied by the word 'Search', with no indication of what fields it matches or whether syntax like CVE IDs is accepted, and 'limit' (default 20, max 100) is never mentioned at all.

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?

States a specific verb and resource: 'Search the Exploit-DB index (46k entries), offline.' The named index and entry count make the scope concrete, and it is distinguishable from siblings like cb_poc or cb_msf by the source it queries. It stops short of explicitly contrasting itself with those siblings, so it falls just 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?

The description gives one routing signal: to fetch source for a numeric id, use the CLI instead. That is genuine when-not guidance, but the alternative is a command-line tool rather than a sibling MCP tool, and there is no guidance on when to prefer cb_exploit over cb_poc, cb_msf, or cb_nuclei. Usage is implied by the name and index rather than stated.

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