Skip to main content
Glama

delete_snapshot

DestructiveIdempotent

Permanently remove a saved snapshot from ServerStorage._TufanSnapshots to free space or tidy up; the live instance remains untouched, and deletion is final.

Instructions

Permanently delete one saved snapshot from ServerStorage._TufanSnapshots to free space or tidy up. Only the checkpoint is removed; the live instance it was taken from is not touched. The deletion is not recorded as a Studio undo step, so treat it as final. Fails if no snapshot has that name; use list_snapshots to check names first.

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

Input Schema

NameRequiredDescriptionDefault
nameYesExact snapshot name, as shown by list_snapshots.
placeNoTarget place (PlaceId or project name). Defaults to the bound/sole connected place.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.1
    • addedInput schema / properties / name / description
      Added value: +"Exact snapshot name, as shown by list_snapshots."
  2. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/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 partly supplied. The description adds valuable behavior beyond the annotations: deletion is permanent, not recorded as a Studio undo step, only the snapshot is removed, and the call fails when the name does not exist.

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?

The description is four sentences with no wasted wording. It is front-loaded with the primary action and scope, then adds the important permanence and validation warnings in a logical order.

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?

For a destructive tool with no output schema, the description covers the essential behavior: what is deleted, what is not affected, that it cannot be undone, and the failure mode. The place parameter's default is delegated to the schema, which is acceptable given full schema coverage.

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%, so the baseline is 3. The description reinforces that the name must be exact and should come from list_snapshots, but this largely repeats the schema's own name description and does not add syntax or format details.

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

Purpose5/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: permanently delete one saved snapshot from ServerStorage._TufanSnapshots. It clearly distinguishes removing the checkpoint from touching the live instance, which separates it from sibling deletion tools like delete_instance.

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

Usage Guidelines4/5

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

It gives clear usage context (free space or tidy up) and directs the agent to list_snapshots to verify the exact name before calling. It falls short of 5 because it does not explicitly state when not to use it or name an alternative cleanup tool beyond list_snapshots for validation.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.