Skip to main content
Glama

Coline

Restore a snapshot

restore_sheet_snapshot
Destructive

Puts a sheet back to a saved snapshot. The current state is kept in history.

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": {
      "workspace": "<workspace>",
      "sheetId": "<sheetId>",
      "snapshotId": "<snapshotId>"
    },
    "name": "restore_sheet_snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
sheetIdYesSheet id from search, fetch or create_sheet.
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
snapshotIdYes

Output Schema

NameRequiredDescriptionDefault
revisionYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is covered. The description adds a genuinely useful behavioral fact beyond them: 'The current state is kept in history,' signalling recoverability and reducing the perceived risk of a destructive operation. It still omits permissions requirements and whether the source snapshot survives the restore.

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?

Two short sentences, zero filler, with the action front-loaded and the safety-relevant consequence second. Every sentence earns its place.

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?

An output schema exists, so return values needn't be explained. However, for a destructive mutation the description should say more about what exactly is overwritten, whether the snapshot can be reused, and any auth requirements; the single history-preservation sentence is helpful but not sufficient.

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 67%; sheetId and workspace are documented with sourcing hints, but snapshotId carries no description. The description's 'saved snapshot' wording gestures at snapshotId but does not say where to obtain it, so it adds little beyond the 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?

The description states a specific verb and resource ('Puts a sheet back to a saved snapshot'), which cleanly separates it from save_sheet_snapshot and list_sheet_snapshots. It does not explicitly name sibling tools or scope boundaries, so it stops short of full sibling differentiation.

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 explicit when-to-use guidance, no prerequisites (such as obtaining a snapshotId via list_sheet_snapshots), and no statement about when not to restore. The only hint is the phrase 'saved snapshot', which implies a prior save step but requires inference.

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