Skip to main content
Glama

Learn the artist's house conventions from a live TD subtree

learn_conventions

Analyze a TouchDesigner node tree to extract naming, colour, topology, and parameter conventions and save them to a vault. Supports dry-run mode to preview without writing.

Instructions

Walk a TouchDesigner subtree under scope_path without mutating TD, infer naming/colour/topology/parameter conventions, and persist them to the configured vault. By default it writes Memory/conventions.md and may merge confident naming/layout signals into Memory/style.md; set dry_run=true to return the extract without disk writes. Requires TDMCP_VAULT_PATH and returns the sampled conventions plus flags showing which notes were written.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dry_runNoIf true, return the extracted conventions but do NOT write the vault note.
observeNoWhich convention families to extract.
max_nodesNoCap on nodes walked (BFS, depth-unlimited until cap).
scope_pathNoRoot COMP whose subtree is sampled. Defaults to /project1./project1
min_supportNoA pattern must appear at least this many times to be recorded.
also_patch_style_memoryNoIf a confident naming/layout signal is found, also merge it into Memory/style.md.
Behavior1/5

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

The description claims 'without mutating TD', which contradicts the annotation readOnlyHint=false, indicating a potential mutation. This contradiction lowers transparency despite other behavioral details like vault writes being disclosed.

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 purpose, then adds detail. Every sentence adds value, though slight redundancy exists (e.g., mentioning default writes twice).

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 tool's complexity (inferring conventions, writing to vault), the description covers key aspects: non-mutation, vault output, dry_run, default behavior, and return type. Missing output schema detail is acceptable.

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 coverage is 100%, so baseline is 3. The description summarizes parameters but does not add significant meaning beyond the schema's descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool infers naming/colour/topology/parameter conventions from a TD subtree and persists them. It specifies the resource and action, but does not explicitly differentiate from sibling tools like 'style_memory'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage by detailing behavior and prerequisites (e.g., dry_run for testing, requires TDMCP_VAULT_PATH), but does not provide explicit guidance on when to use this tool versus alternatives or 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