Skip to main content
Glama

Package a COMP as a .tox in the vault

save_component_to_vault

Save a live TouchDesigner COMP as a reusable .tox file in the Obsidian vault and create a markdown note with load instructions, completing the component packaging loop.

Instructions

Save a live TouchDesigner COMP as a reusable .tox component file inside the Obsidian vault (at /.tox) and write a companion markdown note with frontmatter, a description, and load instructions — completing the build→parameterize→script→package-to-library loop. The saved .tox can later be loaded back with manage_component (load action). Requires a configured TDMCP_VAULT_PATH. The target COMP must exist and be a COMP (not a non-COMP operator).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
comp_pathYesThe COMP to package as a reusable .tox component.
nameNoComponent name (defaults to the COMP's name). Used for the .tox filename and the note title.
folderNoVault subfolder for the .tox + note.Components
tagsNoTags for the note frontmatter (for browse_vault_library).
descriptionNoA short description stored in the note.
preview_topNoOutput TOP to thumbnail for the component note (e.g. <comp_path>/out1). A COMP itself can't be captured (the preview endpoint renders TOPs), so the thumbnail is skipped unless you pass an explicit TOP path here.
thumbnailNoCapture a preview PNG next to the component note and embed it. Set false to skip.
auto_tagNoWhen true, inspect the COMP's child nodes via the bridge and union the auto_tag_library_asset suggestions into the note frontmatter's `tags`.
Behavior4/5

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

The description adds context beyond annotations: it writes files (tox + note), requires environment config, and explains thumbnail capture limitations. Annotations declare readOnlyHint=false and destructiveHint=false, which is consistent.

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?

The description is concise and front-loaded with the primary purpose, but slightly lengthy. It could be tightened without losing clarity.

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 no output schema and 8 parameters, the description covers inputs, side effects (file creation), and workflow integration. Missing explicit mention of return value or success confirmation, but otherwise complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, and the description adds valuable context: default name and folder, explanation of preview_top and auto_tag, and thumbnail behavior. This goes beyond the schema's descriptions.

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 saves a COMP as a .tox in the vault and writes a companion markdown note, completing the library packaging loop. It distinguishes from sibling tools like manage_component (for loading).

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 mentions prerequisites (TDMCP_VAULT_PATH, COMP must exist) and hints at its place in the build-to-library loop, but does not explicitly state when not to use it or compare with alternatives beyond manage_component.

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