Skip to main content
Glama

restore

Destructive

Restore a retained Deep Rest snapshot in your suite with explicit approve=true. Does not touch your own agent memory or tools.

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": {
      "session": "<session>",
      "snapshot_id": "<snapshot_id>",
      "approve": "<approve>"
    },
    "name": "restore"
  }
}

Input Schema

NameRequiredDescriptionDefault
approveYes
sessionYesPrivate bearer capability returned by check_in. Never put it in a URL.
snapshot_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the safety profile is covered. The description adds meaningful scope: it restores a snapshot into the suite and explicitly does not touch the caller's own agent memory or tools, which is useful reassurance. Yet it doesn't disclose irreversibility, what gets overwritten in the suite, or auth requirements beyond the approve flag.

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?

Two short sentences, front-loaded with the action and the required flag, followed by the scope exclusion. Nothing is wasted; the only shortfall is that brevity leaves gaps rather than being over-long.

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

Completeness3/5

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

For a destructive, non-idempotent mutation with no output schema and a largely undocumented schema, the description covers the essential confirmation gate and the non-interference guarantee. It stops short of telling the agent how to obtain snapshot_id, what state is replaced, or whether the operation can be undone.

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 only 33%, and only session has a schema description; approve is constrained by const:true and snapshot_id has only a regex pattern. The description mentions approve=true but adds no meaning for snapshot_id (e.g., where to obtain it, which snapshots are restorable). Some compensation, but not enough for a low-coverage schema.

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?

States a specific verb (restore) and resource (a retained Deep Rest snapshot in your suite), which distinguishes it from siblings like rest, deep_rest_report, and consolidate. It doesn't explicitly contrast with any named sibling, but the resource is specific enough to be unambiguous.

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

Usage Guidelines3/5

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

The description gives the key invocation condition – approve=true must be explicit – which implies this is a deliberate, confirmation-gated action. However, it does not state when to use restore versus rest, consolidate, or preview_consolidation, nor any prerequisites such as where snapshot_id comes from.

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