Skip to main content
Glama
aliphi

touchdesigner-mcp

by aliphi

td_list_operators

List all child operators at a specified path in TouchDesigner to inspect the current network state.

Instructions

List all child operators at a given path in TouchDesigner. Useful for inspecting the current state of a network.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathNoPath to list children of/project1

Implementation Reference

  • server.js:157-177 (registration)
    Registration of the 'td_list_operators' tool via server.tool() with MCP server. The tool lists all child operators at a given path in TouchDesigner.
    server.tool(
      "td_list_operators",
      "List all child operators at a given path in TouchDesigner. Useful for inspecting the current state of a network.",
      {
        path: z
          .string()
          .default("/project1")
          .describe("Path to list children of"),
      },
      async ({ path }) => {
        const code = `
    children = op('${path}').children
    result = '\\n'.join([f"{c.name} ({c.type}) at ({c.nodeX}, {c.nodeY})" for c in children])
    result if result else "No operators found"
    `.trim();
        const result = await tdExecute(code);
        return {
          content: [{ type: "text", text: result }],
        };
      }
    );
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It correctly implies a read-only operation ('list'), but does not explicitly state it is non-destructive or describe any limitations (e.g., depth of listing). The description is adequate but not detailed.

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?

Two concise sentences that front-load the core purpose and follow up with a usage hint. Every sentence is valuable with no redundant phrasing.

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?

With one parameter and no output schema, the description adequately explains what the tool does and when to use it. It could mention the output format (e.g., returns operator names) or depth behavior, but overall it is sufficient for a simple list operation.

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?

The input schema has 100% description coverage for the single parameter 'path' (default '/project1'). The description adds no additional semantics beyond the schema's parameter description, meeting the baseline expectation.

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?

Explicitly states it lists child operators at a given path in TouchDesigner, clearly distinguishing it from siblings like td_create_operator (create) and td_set_parameter (set). The verb 'list' combined with the resource 'child operators' is specific and unambiguous.

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 a clear usage context: 'Useful for inspecting the current state of a network.' While it doesn't explicitly mention when not to use or name alternatives, the context is sufficient for an AI agent to understand when to invoke this tool over others.

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/aliphi/touchdesigner-mcp'

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