Skip to main content
Glama

Save network as a vault recipe

save_recipe_to_vault

Capture a TouchDesigner COMP network and save it as a reusable recipe note in your Obsidian vault. Turn existing patches into templates for later use.

Instructions

Capture an existing COMP's network (child nodes, non-default parameters, wiring, and text/script DAT bodies) by reading TD, then WRITE it as a reusable recipe note in the Obsidian vault at Recipes/.md; list_recipes/apply_recipe then see it alongside the built-in recipes. Use this to turn a patch you already built into a template — to instantiate a template instead, use apply_recipe. Refuses to overwrite an existing note unless overwrite:true. Returns the note path, recipe id, and node/connection counts. Requires a configured TDMCP_VAULT_PATH.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesRecipe id/slug; also the note filename written under Recipes/ in the vault.
comp_pathNoCOMP whose direct children are captured as the recipe./project1
nameNoHuman-friendly title (defaults to the id).
descriptionNoOne-line summary stored in the recipe note's frontmatter (defaults to empty).
tagsNoFree-form tags for searching/filtering the recipe later (defaults to none).
difficultyNoSkill-level label saved in the recipe metadata (defaults to 'intermediate').
overwriteNoWhen false, refuse to replace an existing Recipes/<id>.md note; set true to overwrite it.
preview_topNoOutput TOP to thumbnail for the recipe note (e.g. <comp_path>/out1). Defaults to the comp's first/last TOP child; omit a TOP entirely to skip the thumbnail.
thumbnailNoCapture a preview PNG next to the recipe note and embed it. Set false to skip.
auto_tagNoWhen true, run the auto_tag_library_asset heuristic on the captured network and merge the suggested tags (union, deduped) into the recipe frontmatter before writing.
Behavior5/5

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

The description discloses that the tool reads the current network state and writes to vault. It states it refuses to overwrite unless overwrite:true. It also mentions the required environment variable. Annotations indicate it's not read-only and not destructive, consistent with description.

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 four sentences, each serving a purpose: explaining the action, the use case, the overwrite policy, and the return values. It is front-loaded with the main purpose. No extraneous information, though it could be slightly more concise.

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 (10 parameters, no output schema), the description provides sufficient context: it explains the operation, the return value (path, id, counts), and a prerequisite (env var). It does not detail each parameter, but the schema covers that. It could be improved by differentiating from similar save tools like save_component_to_vault, but overall it is 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 10 parameters have descriptions in the input schema (100% coverage). The tool description does not add new semantic information about individual parameters beyond what is in the schema; it only mentions id and overwrite in passing. Thus the description does not enhance parameter understanding 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 explicitly states the tool captures a COMP's network and writes it as a reusable recipe note in the vault. It distinguishes itself from the sibling apply_recipe by noting that apply_recipe is for instantiating a template. The verb 'save to vault' is clear.

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 description provides clear guidance: use this to turn an existing patch into a template, and use apply_recipe to instantiate a template. It also warns about the overwrite behavior and the requirement for TDMCP_VAULT_PATH. No explicit 'when not to use' but the alternative is provided.

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