Skip to main content
Glama

Operation Restore

operation_restore
Destructive

Restore a journaled report edit or viewer operation when no later edit conflict exists; preview by default and verify the restored state.

Instructions

Restore a journalled edit or viewer operation if no later edit conflicts.

The journal record names its report; that report is resolved automatically and its tab must be open in the MCP Chrome profile. Preview by default. Restoration is itself journaled and verified. Unknown outcomes need inspection first. Runtime-control recovery additionally requires the original browser document; reload/navigation replacement expires it rather than applying old state to a new session.

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": {
      "operation_id": "<operation_id>"
    },
    "name": "operation_restore"
  }
}

Input Schema

NameRequiredDescriptionDefault
dry_runNo
operation_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.5

TDQS

A3.9/5.0
Behavior5/5

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

Annotations only declare destructiveHint=true; the description goes well beyond that by disclosing the preview default, that restoration is itself journaled and verified, the precondition that the target report's tab must be open in the MCP Chrome profile, and the expiry rule for runtime-control recovery after reload/navigation. These are exactly the operational traits an agent needs before invoking a destructive tool.

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 condition, then preconditions and failure modes in a tight sequence. Dense jargon ('journalled', 'runtime-control recovery') costs some readability but every sentence carries information.

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

Completeness4/5

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

For a destructive, precondition-heavy tool the description covers side effects, preconditions, and expiry behavior, and an output schema exists so return values need not be explained. The remaining gap is the undefined operation_id semantics.

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 0%, so the description must carry parameter meaning. It implies dry_run via 'Preview by default' and hints that operation_id refers to a journal record ('The journal record names its report'), but neither parameter is defined explicitly, leaving the identifier's format and scope unstated.

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 and resource ('Restore a journalled edit or viewer operation') plus a gating condition ('if no later edit conflicts'). It does not name the sibling it differs from (operation_get, revision_restore), so an agent must infer the boundary, 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 Guidelines3/5

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

'Preview by default' and 'Unknown outcomes need inspection first' give real when-to-use context, and the latter implicitly routes the agent to an inspection tool first. However, no alternative is named explicitly and there is no statement of when not to restore beyond the conflict condition.

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

Deploy Server

Other Tools