Skip to main content
Glama

recipe_apply

Applies a named recipe with its parameters to the working copy as a single all-or-nothing transaction, so logic changes are validated together and either fully committed or rejected.

Instructions

Applies a recipe with its parameters to the working copy (all or nothing).

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": {
      "name": "<name>"
    },
    "name": "recipe_apply"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
paramsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden of behavioral disclosure. It does add one meaningful trait, the all-or-nothing atomicity of the apply operation, but omits what happens to existing working-copy content, what permissions are required, and what errors or return values look like.

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

Conciseness4/5

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

A single well-formed sentence that front-loads the action and adds the atomicity qualifier at the end. It is efficient, though one more sentence of routing or parameter detail would still earn its place.

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?

This is a mutation tool with no annotations, no output schema, and zero documented parameters. For that complexity level the description is thin: it leaves param semantics, failure behavior, and effect on existing working-copy content unaddressed.

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 schema gives no meaning for 'name' or 'params'. The description mentions applying 'with its parameters' but does not explain the format of the params object, which keys are expected, or whether params is optional.

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 description states a specific verb and resource ('Applies a recipe') and clarifies that it acts on the working copy with parameters. This is clear, though it does not explicitly differentiate from the sibling recipe_list tool.

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 explicit guidance on when to use this tool versus alternatives such as recipe_list, nor any stated prerequisites, exclusions, or context for choosing it. Usage must be inferred from the name alone.

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