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

io.github.kushvinth/crowbar

cb_cwe

Look up CWE definitions by ID or keyword to identify and classify software weaknesses.

Instructions

CWE definitions (id or keyword).

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.5

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden, yet it says nothing about whether the operation is read-only, what a 'definition' record contains, pagination behavior, or error handling for unknown IDs. A lookup tool is presumably a safe read, but that is inferred rather than disclosed.

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

Conciseness3/5

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

The definition is a single parenthetical fragment with zero filler, but that terseness comes at the cost of under-specification rather than disciplined brevity. There is no front-loaded statement of what the tool returns or how it behaves.

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

Completeness2/5

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

With two parameters, no annotations, and no output schema, the description needs to explain the query modes, return shape, and limit behavior. It covers none of these beyond the bare '(id or keyword)' hint, leaving an agent to guess how ID lookup differs from keyword search.

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 coverage is 0%, so the description must compensate for both parameters. It partially does so for 'query' by indicating that either an ID or a keyword is accepted, but 'limit' (default 20, max 100) is never mentioned, leaving its purpose and defaults unexplained in prose.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The fragment 'CWE definitions (id or keyword)' identifies the resource (CWE definitions) and hints at two lookup modes, but there is no verb and no explicit differentiation from siblings like cb_cve or cb_attack, so an agent must infer that this is a CWE lookup tool from the name alone.

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 guidance on when to use this tool versus cb_cve, cb_search, or other lookup siblings, and no prerequisites or exclusions are stated. The only implicit signal is the '(id or keyword)' parenthetical, which is left unelaborated.

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