Skip to main content
Glama

Save network as a vault recipe

save_recipe_to_vault

Save any built TouchDesigner network to your Obsidian vault as a reusable recipe note, enabling you to apply it as a template elsewhere.

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.
nameNoHuman-friendly title (defaults to the id).
tagsNoFree-form tags for searching/filtering the recipe later (defaults to none).
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.
comp_pathNoCOMP whose direct children are captured as the recipe./project1
overwriteNoWhen false, refuse to replace an existing Recipes/<id>.md note; set true to overwrite it.
thumbnailNoCapture a preview PNG next to the recipe note and embed it. Set false to skip.
difficultyNoSkill-level label saved in the recipe metadata (defaults to 'intermediate').
descriptionNoOne-line summary stored in the recipe note's frontmatter (defaults to empty).
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.
Behavior5/5

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

Discloses that it writes to the vault, refuses to overwrite unless overwrite:true, returns the note path/recipe id/counts, and requires a configured vault path. This adds safety and configuration context beyond the annotations (readOnlyHint=false, destructiveHint=false).

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?

Five sentences, each carrying essential information: action, use case, alternative, overwrite guard, return values, and prerequisite. No filler or repetition.

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?

Comprehensive for a write-to-vault tool: covers purpose, usage, side effects, return values, and configuration requirements. With 100% schema coverage, there are no significant gaps in understanding how to invoke this tool correctly.

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 description coverage is 100%, so baseline is 3. The description mentions overwrite:true and Recipes/<id>.md, which slightly reinforces parameter meaning, but it does not add substantial detail beyond what the schema already provides. It does contextualize what is captured (child nodes, wiring, DAT bodies), helping infer parameter intent.

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 it captures a COMP's network and writes it as a recipe note in the Obsidian vault at Recipes/<id>.md. It uses a specific verb+resource pairing and distinguishes from apply_recipe (instantiate a template) and references list_recipes.

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?

Explicitly states when to use this tool: 'Use this to turn a patch you already built into a template — to instantiate a template instead, use apply_recipe.' Also notes the prerequisite of a configured TDMCP_VAULT_PATH.

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/lucasmaher-hash/touch-designer-mcp'

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