Skip to main content
Glama

caldera_create_ability

Create a new adversary ability in MITRE Caldera by specifying ATT&CK tactic, technique, platform, executor, and command.

Instructions

Create a new ability in Caldera.

Args: name: Human-readable ability name (e.g. 'Dump LSASS memory'). tactic: ATT&CK tactic (e.g. 'credential-access', 'discovery'). technique_id: ATT&CK technique ID (e.g. 'T1003.001'). technique_name: ATT&CK technique name (e.g. 'OS Credential Dumping: LSASS Memory'). platform: Target platform — 'windows', 'linux', or 'darwin'. executor: Executor name — 'psh' (PowerShell), 'cmd', 'sh', or 'python'. command: The command to execute. Use #{variable} for Caldera facts. description: Optional description of what the ability does. timeout: Execution timeout in seconds (default 60).

Returns: JSON string with the created ability including its generated ability_id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
tacticYes
technique_idYes
technique_nameYes
platformYes
executorYes
commandYes
descriptionNo
timeoutNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations were provided, so the description carries full burden. It describes the return value but does not disclose side effects, authentication needs, or whether the operation is idempotent. The word 'Create' implies mutation but no further details.

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 description is structured with Args and Returns sections but is somewhat lengthy due to parameter explanations. It could be more front-loaded with the core purpose. Still, it is mostly clear.

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?

The description covers all parameters and the return value, but lacks usage context and behavioral transparency. Although the output schema exists, the description's return note is adequate. Missing contextual completeness for a tool with no annotations.

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

Parameters5/5

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

The schema has 0% description coverage, but the description provides detailed explanations for all 9 parameters, including examples (e.g., 'Dump LSASS memory' for name) and valid values. This adds significant meaning beyond the raw schema.

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

Purpose5/5

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

The description clearly states 'Create a new ability in Caldera.' using a specific verb and resource. It distinguishes from sibling tools like caldera_create_adversary and caldera_create_operation by focusing on abilities.

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?

No guidance on when to use this tool versus alternatives, such as when to create vs. update an ability. The description only explains how to use it, not the decision context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/cowboy-samurai/caldera-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server