Skip to main content
Glama

Local MCP

by com.local-mcp
OverviewDiscussionsAdmin

Recipe Run

recipe_run
Destructive

Executes a recipe end to end: binds params, runs each step's tool in order via the registry, persists the run (see recipe_runs), and returns each step's result plus any markers_path. A step that errors (an error in its answer, or a refusal) stops the run and is reported (stopped_at, with the step's error_key); a step whose tool this Mac does not offer in tools/list is refused (tool_not_advertised). Either stops the run unless that step is marked "optional": true — then the error is recorded in its result and in skipped_optional, and the run continues.

Input Schema

NameRequiredDescriptionDefault
nameYesName of the saved skill (recipe) to run, exactly as recipe_list reports it.
paramsNoParam overrides (merged over the recipe defaults).
confirmNoIgnored; kept for older clients.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / confirm / description
      Previous value: -"Set true to execute a recipe that has state-changing steps; read-only recipes ignore it."New value: +"Ignored; kept for older clients."
  2. Changed1 schema field changed
    • addedInput schema / properties / name / description
      Added value: +"Name of the saved skill (recipe) to run, exactly as recipe_list reports it."
  3. Changed1 schema field changed
    • removedInput schema / properties / name / description
      Removed value: -"Name of the saved skill (recipe) to run, exactly as recipe_list reports it."
  4. Changed1 schema field changed
    • addedInput schema / properties / name / description
      Added value: +"Name of the saved skill (recipe) to run, exactly as recipe_list reports it."
  5. Changed1 schema field changed
    • addedInput schema / properties / confirm
      Added value: +{
+  "description": "Set true to execute a recipe that has state-changing steps; read-only recipes ignore it.",
+  "type": "boolean"
+}
  6. Added

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations, the description discloses important behavior: steps run in order via the registry, the run is persisted, results include each step's output plus markers_path, and errors or unavailable tools stop the run unless the step is optional. It also explains how stopped_at, error_key, tool_not_advertised, and skipped_optional are surfaced.

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?

The description is front-loaded with the core action and then layers in execution, persistence, and error-handling details. It is dense but each sentence carries necessary behavioral information, so it is appropriately sized for a complex execution tool.

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

Completeness5/5

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

For a destructive, open-world execution tool with no output schema, the description provides strong coverage of the run lifecycle, failure semantics, optional-step behavior, persistence, and returned data. The annotations already cover the safety profile, and the description fills in the operational details an agent needs before invoking it.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already explains name, params, and confirm. The description adds only modest meaning by saying params are bound and mentioning markers_path, which is a return value rather than parameter semantics. This meets the baseline for a fully documented 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 states a specific verb and resource: 'Executes a recipe end to end,' and immediately clarifies the execution sequence, persistence, and return behavior. This clearly distinguishes recipe_run from sibling tools like recipe_get, recipe_list, and recipe_runs, which do not execute recipes.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives clear context that this tool is for running a saved recipe end to end, with expected behavior around failures and optional steps. It does not explicitly name alternatives such as recipe_get or recipe_list, so it stops short of full when/when-not guidance.

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

All Local MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources