Skip to main content
Glama

Restore a Recipe Build

restore_recipe_build
DestructiveIdempotent

Restore one archived private recipe build at an exact revision.

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": {
      "build_ref": "<build_ref>",
      "revision": "<revision>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "restore_recipe_build"
  }
}

Input Schema

NameRequiredDescriptionDefault
revisionYes
build_refYes
idempotency_keyYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, readOnlyHint=false and openWorldHint=false, so the safety profile is covered structurally. The description adds only the preconditions 'archived' and 'at an exact revision'; it says nothing about what a restore overwrites, whether an existing live build conflicts, or what permissions are needed. That is thin but not contradicting the annotations.

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 front-loaded sentence with no filler and no redundant restatement of the title. It is efficient, though the brevity is partly achieved by omitting information that matters for a destructive three-parameter call.

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?

For a destructive, idempotency-keyed mutation with three required and fully undocumented parameters, the description is insufficient; an output schema exists so return values need no explanation, but preconditions, idempotency behavior, and failure modes are all missing.

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 description carries the burden and largely fails it. 'Exact revision' gives a hint that revision must be a precise identifier, but build_ref and especially idempotency_key — a required parameter whose retry semantics materially affect calling behavior — are never mentioned.

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 names a specific verb (restore), resource (archived private recipe build), cardinality (one) and scope (an exact revision), which is enough to distinguish it from the get_/list_/commit_ siblings. It stops short of naming any adjacent operation, but the action itself is unambiguous.

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 when-to-use guidance, no prerequisite statement, and no alternative named. The word 'archived' hints that the target must already be archived, but the agent is left to infer this rather than being told it.

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