Skip to main content
Glama

Coline

Sheet snapshots

list_sheet_snapshots
Read-onlyIdempotent

A sheet's saved versions.

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": "list_sheet_snapshots"
  }
}

Input Schema

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

Output Schema

NameRequiredDescriptionDefault
snapshotsYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

C2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered elsewhere. The description adds nothing beyond that: no word on pagination, ordering (newest first?), snapshot retention, or permissions needed to read version history.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Only one short fragment, so there is no wasted wording, but this is under-specification rather than conciseness. It lacks a verb and any structure that would front-load the key fact that this is a read/list operation over version history.

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

Completeness2/5

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

An output schema and rich annotations reduce what the description must carry, and the parameters are covered by the schema. Still, for a version-history tool an agent needs to know whether results are paginated, ordered, and what a snapshot represents; none of that is present, leaving the definition thin relative to its complexity.

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 description coverage is 100%, and both parameters (sheetId, workspace) are fully documented in the schema, so the baseline of 3 applies. The description adds no extra meaning, but it is not required to given the schema quality.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"A sheet's saved versions" is a noun phrase that essentially restates the name and title rather than stating the action (list) and resource. It does clarify what a "snapshot" is, which is marginally more than a pure tautology, but it never says the tool returns a list of them or distinguishes it from compare_sheet_snapshot, restore_sheet_snapshot, or save_sheet_snapshot.

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

Usage Guidelines1/5

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

No when-to-use guidance at all: no indication of when to call this versus compare_sheet_snapshot (to diff versions) or restore_sheet_snapshot (to roll back), and no prerequisites or ordering advice. The agent must infer the entire usage model from the sibling names.

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