Skip to main content
Glama

Coline

Compare with a snapshot

compare_sheet_snapshot
Read-onlyIdempotent

What changed in a sheet since a saved snapshot.

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": "compare_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
diffYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is fully covered elsewhere. The description adds no behavior of its own — nothing about what the diff covers, cost, or whether non-sheet-level changes are included.

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

Conciseness3/5

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

One short sentence with no padding, so it is certainly concise, but it is under-specified rather than well-structured — there is no verb-first framing or scoping clause to anchor the agent.

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?

With an output schema present, return values need no explanation, but three required parameters at 67% coverage still leave gaps the description should fill. For a read-only comparison tool, the agent is told what it asks but not enough about the inputs to invoke it confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 67% and snapshotId carries no description in the schema, yet the description says nothing about any of the three required parameters. It neither disambiguates where snapshotId comes from nor adds format context 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 names the resource (a sheet) and the comparison basis (a saved snapshot) and frames the outcome as change detection, which separates it from save/restore/delete snapshot siblings. It lacks a leading verb, so it reads as a question fragment rather than a stated operation.

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 statement of when to use this instead of list_sheet_snapshots, list_sheet_history, or read_sheet, and no prerequisites such as needing a previously saved snapshot. The snapshot requirement is only implied by the wording.

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