Get errors and warnings: get_op_errors with recurse=true on the suspected operator and its children
Inspect the operator: get_op to see type, family, parameters, inputs, outputs, children
Check connections: get_connections to verify input/output wiring is correct
Read DAT content: get_dat_content if the operator is a DAT with script errors
Check parameters: get_parameter on specific parameters that might be misconfigured
Check performance: get_op_performance if the issue is cook-time related

Common Error Patterns

Missing input: Operator requires a specific input type — check connections
Script error in DAT: Read the DAT content and fix the Python/expression
Parameter out of range: Check parameter values against valid ranges
Missing operator reference: An expression or parameter references a non-existent operator
Cook error: The operator can't process its inputs — check input data types match expectations

Mais deste repositório

mesmo repositório

mcp-tools-reference

dylanroscover/Embody

MUST READ before first MCP tool call in a session. Complete Envoy tool catalog with parameters and usage.

2026-06-07118

run-tests

dylanroscover/Embody

Run Embody's test suite and write new tests (Embody development)

2026-06-07118

create-operator

dylanroscover/Embody

MUST READ before calling create_op. Contains required verification, positioning, and error-checking steps.

2026-05-27118

td-api-reference

dylanroscover/Embody

MUST READ before writing TD Python via execute_python, set_dat_content, or edit_dat_content. API reference for parameters, storage, operators, threading.

2026-05-27118

multi-instance

dylanroscover/Embody

Workflow for running multiple TD instances with Envoy, switching between them, and understanding the instance registry.

2026-05-21118

externalize-operator

dylanroscover/Embody

MUST READ before calling externalize_op or save_externalization. Required workflow steps.

2026-04-13118

name	debug-operator
description	TRIGGER when operator errors appear or user reports broken behavior. Systematic diagnosis workflow.

Debug Operator Workflow

Systematic approach to diagnosing TD operator errors:

Get errors and warnings: get_op_errors with recurse=true on the suspected operator and its children
Inspect the operator: get_op to see type, family, parameters, inputs, outputs, children
Check connections: get_connections to verify input/output wiring is correct
Read DAT content: get_dat_content if the operator is a DAT with script errors
Check parameters: get_parameter on specific parameters that might be misconfigured
Check performance: get_op_performance if the issue is cook-time related

Common Error Patterns

Missing input: Operator requires a specific input type — check connections
Script error in DAT: Read the DAT content and fix the Python/expression
Parameter out of range: Check parameter values against valid ranges
Missing operator reference: An expression or parameter references a non-existent operator
Cook error: The operator can't process its inputs — check input data types match expectations