Skip to main content
Glama

td_restore_snapshot

Destructive

Restore parameter values from a saved snapshot in TouchDesigner. Use dry-run to preview changes or limit to specific nodes with partial.

Instructions

Restore parameter values from a previously saved snapshot.

This tool replays the parameter values captured in the snapshot back onto the live TouchDesigner network. It restores parameter values only — it does not add, remove, or rewire nodes. For structural rollback (topology changes such as added/deleted nodes or connection changes) use TouchDesigner's native Ctrl+Z undo stack instead.

Use dry_run=True to preview what would be changed without applying anything. Supply partial with a list of node paths to limit the restore to a subset of the snapshot.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dry_runNoReturn diff only without applying.
partialNoOptional subset of node paths. When provided, only these nodes (and no others) have their parameters restored from the snapshot.
snapshot_idYesSnapshot id to restore parameter values from.
param_semantics_policyNoDocs-grounded parameter safety policy for restored snapshot params. 'warn' preserves restore behavior with attached findings; 'block' refuses unsafe parameter restores before any live mutation.warn

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Description adds value beyond annotations by clarifying that only parameter values are restored (no node addition/removal) and offers preview via dry_run. It aligns with destructiveHint=true and adds safety context.

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 concise (4 sentences), front-loaded with purpose, and each sentence contributes meaningful information without redundancy.

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?

Given the complexity (restore with safety options) and rich schema/annotations, the description adequately explains behavior, usage, and alternatives. It could mention the param_semantics_policy, but schema covers it.

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 coverage is 100% with detailed descriptions for all parameters. The description reiterates dry_run and partial usage, which adds context but does not introduce new semantics beyond the schema.

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 clearly states the tool restores parameter values from a snapshot, specifies it does not modify structure, and distinguishes it from Ctrl+Z for topology changes, differentiating it from siblings like td_snapshot_scene.

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 provides explicit guidance: use Ctrl+Z for structural rollback, and mentions dry_run for preview and partial for limiting scope. It lacks explicit 'do not use' scenarios but covers key usage context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/dreamrec/TDPilot'

If you have feedback or need assistance with the MCP directory API, please join our Discord server