Execute complex data transformations by chaining CyberChef operations into a single recipe. Handle multi-step encoding, encryption, and forensic analysis tasks in one call.
Execute a CyberChef recipe. Use this for complex chains of operations.
| Name | Required | Description | Default |
|---|---|---|---|
| input | Yes | The input data | |
| recipe | Yes | List of operations to perform |
Changes observed during successful MCP inspections.
v3.6.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations mark this as destructive and potentially open-world, but the description itself adds no behavioral context beyond 'execute.' It does not mention whether output is returned synchronously, whether recipes can trigger external side effects, or what operational consequences the destructiveHint refers to. Since it adds no insight beyond the annotations, it under-delivers for an execution tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is only two short sentences with no wasted words. It front-loads the main action and follows with a brief usage hint. Nothing repeats the schema, and every sentence earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a tool with no output schema, potentially destructive behavior, and broad execution capabilities, this description is too thin. It does not describe return values, error behavior, execution limits, or how it differs from related tools like cyberchef_recipe_execute. The schema covers inputs well, but not the execution context an agent needs.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, and the schema already documents the input and recipe parameters, including the recipe's op/args shape and a pointer to cyberchef_describe_operation. The tool description adds no parameter-level detail, so it earns the baseline score of 3 rather than being penalized for a schema gap.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states a concrete action and resource: it executes a CyberChef recipe. It also adds a usage scope by mentioning 'complex chains of operations.' However, it does not explicitly distinguish this from sibling tools like cyberchef_recipe_execute, which may also sound recipe-related, so it is not fully differentiated.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The phrase 'Use this for complex chains of operations' provides a clear, explicit when-to-use context. It stops short of naming exclusions or alternatives such as cyberchef_magic or cyberchef_recipe_execute, so there is no when-not-to-use guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.