Skip to main content
Glama

Coline

Delete a snapshot

delete_sheet_snapshot
DestructiveIdempotent

Deletes 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": "delete_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
deletedYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

C2.2/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered structurally. The description adds nothing on top of that: it does not say whether deletion is permanent or whether the snapshot can still be restored afterward, nor whether anything referencing the snapshot breaks. For a destructive operation this is a missed opportunity.

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?

The single sentence is front-loaded and free of waste, so it is structurally clean. However, brevity here reads as under-specification rather than precision — the sentence is too short to carry any of the information an agent needs for a destructive tool.

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 and annotations fully disclose the destructive/idempotent nature, which lowers the burden on prose. Still, for a destructive delete with a partially documented schema, the description should distinguish this tool from the restore/compare siblings and clarify the snapshotId source; neither is present.

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?

At 67% schema coverage, sheetId and workspace are documented in the schema, but snapshotId has no description anywhere. The description adds zero parameter meaning — it does not say where a snapshotId comes from (e.g., list_sheet_snapshots) or that all three identifiers must belong to the same workspace.

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?

"Deletes a saved snapshot." restates the tool name (delete_sheet_snapshot) and title ("Delete a snapshot") with no additional specificity. The verb+resource is identifiable, so it is not misleading, but it adds no distinguishing detail versus restore_sheet_snapshot or compare_sheet_snapshot beyond the word 'delete' already in the name.

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 guidance on when to use this versus restoring or comparing a snapshot, no prerequisites (e.g., ownership/permission requirements to delete), and no warning about irreversibility in the text. The agent is left to infer everything from the tool name alone.

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