Skip to main content
Glama

Undo a recipe change

restore_revision
Destructive

Roll a recipe back to an earlier revision (ingredients, steps, filing, all fields). Overwrites the current fields with the old revision's; the current version is kept as a revision, so it can be undone with another restore_revision. Get revision_no from list_history first. Needs edit access; blocked on read-only accounts. Returns the restored recipe.

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": {
      "id": "<id>",
      "revision_no": "<revision_no>"
    },
    "name": "restore_revision"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesRecipe id (UUID) from search_recipes or an earlier result
revision_noYesRevision number from list_history, e.g. 3

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the destructiveHint=true annotation by explaining exactly what is overwritten, that the pre-restore version is preserved as a revision, and that the operation is therefore reversible. It also discloses the permission requirement (edit access, blocked on read-only accounts) and the return value.

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

Conciseness5/5

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

Four tight sentences with no filler: operation, overwrite semantics, reversibility, prerequisite, permission gate, and return value, in that order. Nothing is buried or repeated.

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 two-parameter mutation without an output schema, the description covers prerequisites, access constraints, destructiveness and recoverability, and the return value — everything an agent needs to invoke it safely.

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?

With 100% schema description coverage, both parameters are already documented in the schema, including that revision_no comes from list_history. The description reinforces the source but adds no format or edge-case detail beyond the structured fields.

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?

States a specific verb and resource — rolling a recipe back to an earlier revision — and enumerates the scope of fields affected (ingredients, steps, filing, all fields). This clearly separates it from save_recipe, update_recipe, and delete_recipe in the sibling list.

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?

Explicitly routes the agent to list_history to obtain revision_no before calling, and describes the undo path via another restore_revision. It lacks an explicit when-not statement (e.g., use update_recipe for manual field edits), so it falls just short of full alternative coverage.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources