Skip to main content
Glama

Restore an archived Gambit

restore_gambit
Idempotent

Restore one of YOUR archived Gambits (requires api:account) to the state it was archived from; a live one comes back tracked. case_id comes from list_gambits with archived=true. Only possible until its purge_at (3 days after archiving). One that is not yours, or already purged, answers 404. If another live Gambit already follows the same setup the call answers 409 with code case_restore_conflict and live_case_id (when known): tell the user they already track it there. Returns the Gambit in full, as get_gambit does. This places no order. The response carries app_url, this Gambit's screen.

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

Input Schema

NameRequiredDescriptionDefault
case_idYesan archived Gambit id from list_gambits with archived=true (UUID)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations: names the required auth scope (api:account), the 3-day purge window, the 409 payload shape (code case_restore_conflict plus live_case_id when known), that the call places no order, and that the response includes app_url. The annotations cover safety hints, and the description adds the operational and error-handling context they cannot express.

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?

Front-loaded with the action and its scope, then layered preconditions, failure modes, and return format with no filler sentences. The semicolon-chained clauses make it dense and slightly harder to scan than a short bulleted structure would be, but every sentence carries information.

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?

With no output schema, the description still explains the return value ("the Gambit in full, as get_gambit does" plus app_url), and it covers preconditions, time limit, and both error paths. Nothing an agent needs to invoke this correctly is missing.

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 coverage is 100% for the single parameter, and the description's provenance note ("from list_gambits with archived=true") largely restates the schema's own case_id description. It adds no format or edge-case detail beyond the schema, so the baseline of 3 applies.

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 ("Restore ... archived Gambits") plus scope ("one of YOUR", ownership required via api:account) and the resulting state ("to the state it was archived from"). An agent can distinguish this from archive_gambit and get_gambit without opening a schema.

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

Usage Guidelines5/5

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

Gives explicit preconditions and where the input comes from ("case_id comes from list_gambits with archived=true"), a hard time limit ("Only possible until its purge_at (3 days after archiving)"), and when-not cases with exact failure semantics (404 for not-yours/purged, 409 for a conflicting live Gambit). It even prescribes the user-facing action on 409.

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