mcp-for-maya

Overview Schema Source Related Servers Discussions Admin

Scene Checkpoint List

scene_checkpoint_list

Read-onlyIdempotent

Lists saved checkpoints for the current Maya scene, including workspace ad-hoc snapshots for untitled scenes, so you can review available rollback points before restoring.

Instructions

List all saved checkpoints for the current scene state.

Boundary: Disambiguated from scene_checkpoint (write a new checkpoint) and scene_rollback (open one and rebind the scene to it) — scene_checkpoint_list only reads what is already on disk.

Saved scenes list <scene_dir>/checkpoints; untitled scenes list the workspace ad-hoc snapshots (adhoc flag per entry).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "scene_checkpoint_list"
  }
}

Input Schema

Name	Required	Description	Default
`session_key`	No	Maya session key.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.1Sep 30, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds genuinely non-structured behavior: saved scenes read <scene_dir>/checkpoints while untitled scenes fall back to workspace ad-hoc snapshots, with an adhoc flag per entry. It stops short of noting any auth/session prerequisite for the session_key.

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

Conciseness4/5

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

Front-loaded with the action, then the disambiguation boundary, then the storage nuance — a sensible ordering with no filler. The final sentence is dense but load-bearing; minor cost is that it packs two distinct rules into one line.

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

Completeness5/5

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

An output schema exists, so return values need no explanation, and the description still flags the adhoc-per-entry field that an agent would otherwise misread. For a zero-required-param read tool, nothing needed to call it correctly is missing.

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?

With a single optional parameter at 100% schema description coverage, the schema does the documentation work. The description implies the scene/session context that determines which store is listed but adds nothing about session_key's format or default behavior, so baseline 3 applies.

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 ('List') and resource ('all saved checkpoints for the current scene state'), then immediately separates it from the two similarly named siblings. An agent can distinguish this from scene_checkpoint and scene_rollback without opening any schema.

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

Usage Guidelines5/5

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

The explicit 'Boundary:' line names both alternatives (scene_checkpoint for writing, scene_rollback for rebinding) and gives the condition that selects this tool: 'only reads what is already on disk.' That is when-to-use and when-not-to-use in one sentence.

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