Skip to main content
Glama

Scaffold extension class

scaffold_extension

Give a TouchDesigner COMP a Python extension class: create a Text DAT, wire it into an extension slot, optionally promote for direct member calls, and reinitialize.

Instructions

Give a COMP a Python extension class: create a Text DAT holding the class (with optional method stubs), wire it into an extension slot, optionally promote it (so members are callable directly on the COMP), and reinitialize. The other half of making a generated network reusable — pair with add_custom_parameters (knobs) and manage_component (save as .tox).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slotNoExtension slot (1–8) — a COMP can hold several extensions.
methodsNoOptional method-name stubs to add to the class (each takes only `self`).
promoteNoPromote the extension so its members are callable directly on the COMP (op.Method()).
comp_pathYesThe COMP to give a Python extension class.
class_nameYesExtension class name, e.g. 'WidgetExt' (capitalized to a valid identifier; must already be identifier-safe).
Behavior4/5

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

Despite annotations already indicating a non-read-only, non-destructive, open-world mutation, the description adds meaningful behavioral details: creating a Text DAT, wiring into a slot, optional promotion, and reinitialization. It discloses the main side effects without contradicting the 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?

The description is concise (two sentences) and front-loaded with the core action. Every phrase earns its place: the action list is specific, and the pairing guidance is valuable without bloating the text.

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?

The description covers the main workflow steps (create, wire, promote, reinit) for a mutation tool, and the schema fully documents parameters. It is sufficiently complete for an agent to understand when and how to invoke the tool, though it omits potential edge cases like overwriting an existing extension in the slot.

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 all parameters, so the baseline is 3. The tool description restates the meaning of `methods` and `promote` but does not add new syntax or constraints beyond what the schema already provides, making its contribution marginal.

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 states a specific verb and resource: 'Give a COMP a Python extension class', and enumerates the concrete steps (create Text DAT, wire into slot, promote, reinitialize). It also distinguishes itself from related tools by naming companion tools (`add_custom_parameters`, `manage_component`), making its role clear.

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?

The description provides clear context: it is 'the other half of making a generated network reusable' and explicitly recommends pairing with `add_custom_parameters` and `manage_component`. However, it does not state when NOT to use this tool versus other scaffold tools, so it lacks explicit exclusions.

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