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

io.github.kushvinth/crowbar

cb_attack

Look up MITRE ATT&CK techniques across enterprise, mobile, and ICS domains to identify adversary tactics and support threat analysis.

Instructions

MITRE ATT&CK technique lookup (enterprise, mobile, ics).

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes
domainNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.5

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and largely fails it. 'Lookup' implies a read-only operation, but nothing states whether results are paginated (despite a limit parameter), how many results to expect, or what happens when the query matches nothing.

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?

One short phrase with zero redundancy, so nothing needs trimming. However, the brevity comes at the cost of under-specification rather than earned conciseness — the single clause leaves the query semantics and result behavior undefined.

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 three undocumented parameters, no annotations, and no output schema, the definition leaves too much for the agent to guess. A lookup tool needs at minimum a note on accepted query formats and the meaning of the domain and limit controls.

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 all three parameters. It hints that domain takes enterprise/mobile/ics values, which is genuinely useful, but it says nothing about whether query expects a technique ID (T1059), a name, or free-text, nor what limit truncates.

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 phrase 'MITRE ATT&CK technique lookup' names a specific resource and operation, and the parenthetical '(enterprise, mobile, ics)' scopes which ATT&CK domains are covered. It implicitly distinguishes the tool from siblings like cb_cve and cb_cwe by naming the framework, though it never explicitly contrasts with them.

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 when-to-use guidance, no mention of prerequisites, and no pointer to alternatives for related lookups (e.g. CVE or CWE tools in the sibling set). The agent must infer from the name alone whether this is for technique IDs, keyword search, or mapping.

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