Skip to main content
Glama

Export externalized .tox tree (git-diffable)

export_externalized_tree
Destructive

Export a TouchDesigner COMP as a git-diffable externalized .tox tree. Each component becomes an individual .tox file, enabling per-node diffs in version control.

Instructions

Save a COMP as a git-diffable externalized .tox tree using TouchDesigner's 'save external' (COMP.saveExternalTox). Instead of one opaque binary, the component — and, with recurse=true, every descendant COMP — is written to its own .tox file on disk with its externaltox parameter pointed at that file, so a version-controlled project shows per-node diffs. Writes files under out_dir (destructive) and mutates the live COMP's externaltox pars. out_dir is passed to the TouchDesigner process, so it must be a path that process can write to.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoRoot .tox stem. Defaults to the last path segment of comp_path.
out_dirYesLocal folder to write the externalized .tox tree into. Passed to TouchDesigner as the save target, so it must be reachable from the TD process's filesystem.
recurseNoWhen true, externalize every descendant COMP too (each becomes its own .tox file), so the whole subtree is git-diffable. When false, only the root COMP is externalized.
comp_pathYesFull path of the COMP to externalize (its .tox is written to out_dir/<name>.tox).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
compYesEchoed COMP path that was externalized.
countYesNumber of COMPs externalized.
recurseYesWhether descendant COMPs were externalized too.
root_toxYesAbsolute path of the root externalized .tox.
warningsYes
externalizedYesEach COMP that now points at an external .tox file (node path → externaltox path).
Behavior5/5

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

The description explicitly mentions that the tool writes files to out_dir (destructive) and mutates the live COMP's externaltox parameters, which aligns with and adds detail beyond the annotations (destructiveHint=true, readOnlyHint=false). No contradictions.

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 (3 sentences) and front-loaded with the main action. Every sentence adds value, avoiding fluff or repetition.

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 presence of an output schema (not shown), the description does not need to explain return values. It covers the key effects (writing files, mutating parameters), constraints (out_dir path requirement), and the optional recurse behavior. Missing example or mention of expected output, but overall adequate.

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?

All parameters have schema descriptions (100% coverage), so baseline is 3. The description adds high-level context for parameters but does not significantly enhance understanding of individual parameter syntax or options 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's purpose: to save a COMP as a git-diffable externalized .tox tree using TouchDesigner's 'save external' method. It specifically contrasts with opaque binary saves, distinguishing it from export_look_tox and other export siblings.

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?

The description explains when to use: for version-controlled projects to get per-node diffs. It mentions destructive nature and mutation of externaltox pars but does not explicitly list alternative tools or conditions when not to use it.

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/Pantani/tdmcp'

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