Skip to main content
Glama

td_get_node_detail

Read-onlyIdempotent

Retrieve detailed information about a TouchDesigner node, including type, errors, warnings, parameters, and optional notes and hints.

Instructions

Get detailed info about a node (type, errors, warnings, parameters).

The parameters dict is capped at param_limit entries (default 50, hard ceiling 200) — full COMP serialization can blow past 80 KB. Use td_get_params with name/page filters when you need the rest.

When include_notes=True, any markdown note saved via td_component_notes for this path is attached as a note field.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesAbsolute path to the node (e.g. '/project1/noise1', '/project1/geo1/sphere1')
param_limitNoMax parameters to serialize. Default 50; hard cap 200. If the node has more, the response sets parameters_truncated=true and parameters_total to the real count. Use td_get_params for the rest.
include_hintsNoIf True, attach a ``hints`` block via td_get_hints scoped to the inspected node's op_type and the 'inspect' response surface. Auto-injection still fires when surface-restricted hints exist for this op_type.
include_notesNoIf True, look up any per-COMP note saved via td_component_notes for this path and surface it as ``note`` in the response. Default False to keep response sizes stable.
response_formatNoOutput formatjson

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

While annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, the description adds behavioral details: the parameter cap (default 50, hard ceiling 200), potential size blowup ('80 KB'), and the note attachment behavior when include_notes=True. These add value beyond 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 three well-structured sentences. It opens with the core purpose, then details limitations and alternatives, and ends with optional behavior. No unnecessary words.

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?

Given the tool's complexity (5 parameters, output schema exists), the description covers all key behavioral traits: parameter cap, note retrieval, hints toggle, and alternative when more params are needed. It is sufficient for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema already covers all parameters with descriptions (100% coverage). The description adds context: the param_limit cap explanation including the 80 KB warning, and that include_notes fetches notes via td_component_notes. This enhances understanding beyond the schema.

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 the purpose: 'Get detailed info about a node (type, errors, warnings, parameters).' It distinguishes this tool from the sibling td_get_params by explaining when to use the sibling for full parameter retrieval.

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 provides guidance: 'Use td_get_params with name/page filters when you need the rest.' Also mentions that param_limit caps the parameter dict, implying when to use the alternative for more than 200 parameters.

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/dreamrec/TDPilot'

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