Skip to main content
Glama

List Playground canvas snapshots

playground_canvas_snapshots_list
Read-onlyIdempotent

List recent whole-canvas snapshots taken before agent runs, MCP writes, reverts and restores. Read-only. Returns snapshot IDs, revisions, reasons and node counts.

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

Input Schema

NameRequiredDescriptionDefault
projectIdYesID of the Playground project chosen for this task; obtain it from project creation, an explicit project link or current context.

Output Schema

NameRequiredDescriptionDefault
snapshotsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint=true, destructiveHint=false, idempotentHint=true, openWorldHint=false), so the description only needs to add context, which it does by explaining what events generate snapshots and what each entry contains. The remaining gap is that 'recent' is undefined — no count limit, time window, or pagination behavior is disclosed, which matters for a list tool.

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?

Three short sentences: purpose and scope first, safety second, return shape third. No filler, no restatement of the title, and the most decision-relevant information is front-loaded.

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 single-parameter, read-only list tool with an output schema, this is nearly complete: scope, safety, and return fields are all covered. The one substantive omission is result-size behavior — whether the list is truncated, ordered by time, or paginated — which an agent needs to interpret 'recent' correctly.

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 the single projectId parameter carries a detailed description including how to obtain it, so the schema does the work. The tool description adds no further meaning about the parameter or about what happens if the project has no snapshots. Baseline 3 is appropriate.

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?

States a specific verb and resource ('List recent whole-canvas snapshots') plus the exact scope of what a snapshot captures: taken before agent runs, MCP writes, reverts and restores. The explicit 'Read-only' tag separates it from playground_canvas_snapshot_restore, so an agent can pick between listing and restoring without opening either schema.

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 trigger conditions ('taken before agent runs, MCP writes, reverts and restores') imply the tool is for inspecting recent restore points, but the description never says when to call it — e.g. before a restore, or after an unexpected agent write. No alternative is named and no prerequisite beyond the project ID is stated. Usage is inferable but not spelled out.

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.