Skip to main content
Glama

Bind a Text DAT to a vault note

bind_vault_text

Create a Text DAT in TouchDesigner linked to a vault note, loading its text into TD and syncing live with Obsidian edits for your visuals.

Instructions

CREATE a Text DAT in TouchDesigner whose file parameter points at a vault note, so the note's text loads into TD (and, with sync:true, stays live as you edit it in Obsidian) — turning the vault into the text/lyrics source for your visuals. Side effect is node creation in TD plus reading the note file; it does not write to the vault. Wire the DAT into a Text TOP to render it. Returns the DAT path, the resolved note, the absolute file path, and whether sync is on. Requires a configured TDMCP_VAULT_PATH.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoName for the Text DAT (defaults to a slug of the note).
noteYesVault-relative note to read into TD (lyrics, poetry, any text content).
syncNoKeep the DAT synced to the file, so edits in Obsidian show up live in TD.
parent_pathYesParent COMP to create the Text DAT inside.
Behavior5/5

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

Beyond annotations, the description details side effects (node creation + file read), explicitly states it does not write to the vault, explains sync behavior, and lists return values. This adds significant context over the readOnlyHint/destructiveHint/openWorldHint annotations.

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?

Concise at 4 sentences, action-first opening, includes side effects, usage, returns, and requirement without extraneous detail. Every sentence contributes.

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?

For a tool without an output schema, the description adequately explains return values, side effects, and prerequisites. It covers the full workflow and boundaries, making it sufficient for an agent to invoke 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 covers 100% of parameters with descriptions, so baseline is 3. The description does not add much parameter-level meaning; it mentions sync's live-editing effect, but the schema already states that. No new parameter insights are provided.

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 opens with 'CREATE a Text DAT in TouchDesigner whose file parameter points at a vault note', specifying the exact action and resource. It clearly differentiates from sibling tools like create_td_node or edit_dat_content by focusing on vault-note-binding behavior.

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?

Provides clear context: use this to turn the vault into text/lyrics source for visuals, and mentions a workflow step (wire into Text TOP). It notes prerequisites (TDMCP_VAULT_PATH) and boundaries (does not write to vault), but does not explicitly name alternative tools or when-not-to-use conditions.

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