Skip to main content
Glama

Coline

Save a sheet snapshot

save_sheet_snapshot

Saves the whole sheet as a named version to compare with or restore later.

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>",
      "name": "<name>"
    },
    "name": "save_sheet_snapshot"
  }
}

Input Schema

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

Output Schema

NameRequiredDescriptionDefault
snapshotNo

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=false, so the mutation profile is covered. The description adds that the entire sheet (not a range) is captured and that the version is named, but stays silent on whether reusing a name overwrites an existing snapshot, any snapshot-count limits, or permission requirements.

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?

A single sentence with zero filler, front-loaded with the verb and scope. Every clause ('whole sheet', 'named version', 'compare with or restore later') 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?

With an output schema present, return values need no explanation, and the three required parameters are simple flat strings. The description conveys scope and purpose adequately; only edge-case behavior like duplicate names or retention limits is left uncovered, which is a minor gap for a tool this simple.

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 in the schema, while 'name' has only length bounds. The description's 'named version' partially compensates by revealing that name is a human-readable label for the version, but it adds no format, uniqueness, or length guidance beyond that.

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 gives a specific verb ('Saves') and resource ('the whole sheet') plus the resulting artifact ('a named version'), so the agent knows exactly what is produced. It does not name or distinguish any sibling, so it falls short of a 5.

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 phrase 'to compare with or restore later' implies the intended workflow and points conceptually at compare_sheet_snapshot and restore_sheet_snapshot, but no alternative is named and there is no when-not guidance. Usage is implied rather than stated.

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