Skip to main content
Glama

Get operator runtime state

get_node_state_runtime
Read-only

Inspect a single operator's runtime telemetry including cook time, GPU memory, errors, and optional Info CHOP channels for deep per-op diagnostics.

Instructions

Read-only: inspect a single operator's runtime telemetry — cook time, cook count, last-cook frame, resolution (TOPs), channel/sample counts (CHOPs), GPU memory usage, cook errors, and optional Info CHOP channels via include_info_chop. Complements get_td_performance (which aggregates cook times across a network) by providing deep per-op detail for the 'why is it black / why is it slow' diagnostic loop. Returns {path, type, family, cook_time_ms, cook_count, last_cook_frame, resolution, num_chans, num_samples, gpu_memory, info_chop?, errors[], warnings[], extra}. Attribute names are flagged UNVERIFIED and vary by TD build; the extra map records which attrs were actually present for live confirmation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesFull path of the operator to inspect (e.g. '/project1/noise1').
include_info_chopNoWhen true, create a temporary Info CHOP beside the operator and sample its channels for deeper per-op telemetry. Fail-forward: unreadable Info CHOP data becomes warnings.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesEchoed operator path.
typeYesOperator type string (e.g. 'noiseTOP').
familyNoOperator family: TOP, CHOP, SOP, DAT, COMP, MAT, etc.
cook_time_msNoLast cook duration in milliseconds (op.cookTime * 1000). UNVERIFIED attr name.
cook_countNoTotal number of times the op has cooked (op.totalCooks / op.cookCount). UNVERIFIED.
last_cook_frameNoAbsolute frame number of the last cook (op.cookAbsFrame). UNVERIFIED attr name.
resolutionNo[width, height] for TOPs (op.width, op.height). UNVERIFIED.
num_chansNoNumber of channels for CHOPs (op.numChans). UNVERIFIED.
num_samplesNoNumber of samples per channel for CHOPs (op.numSamples). UNVERIFIED.
gpu_memoryNoGPU memory used in bytes for TOPs (op.gpuMemory). UNVERIFIED attr name.
errorsYesCook errors from op.errors(recurse=False).
warningsYesBridge-level warnings about unreadable attributes.
info_chopNoOptional Info CHOP telemetry when include_info_chop=true.
extraNoAdditional Info attributes found via getattr probing — allows live-validation to confirm real attr names.
Behavior5/5

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

Annotations already provide readOnlyHint and destructiveHint; description confirms read-only and adds context: include_info_chop creates a temporary Info CHOP with fail-forward warnings, and the extra map records which attrs were present. No contradictions.

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 sentences (plus UNVERIFIED note) that front-load the purpose and key details. Every sentence earns its place; no fluff.

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?

With output schema present, description covers all necessary context: lists return fields, notes temporary side-effects of include_info_chop, and explains the extra map. Complete for diagnostic use.

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?

Schema coverage is 100%, baseline 3. Description adds meaning: path example and clear explanation of include_info_chop's behavior (creates temp Info CHOP, fails forward with warnings). Provides value beyond 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?

Clearly states it is a read-only inspection of a single operator's runtime telemetry, listing specific metrics like cook time, cook count, etc. Distinguishes from sibling tool 'get_td_performance' by explicitly stating it provides deep per-op detail versus aggregate network-level data.

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 says when to use: for diagnosing 'why is it black / why is it slow' per operator. Mentions alternative 'get_td_performance' for aggregate cook times. Also warns that attribute names are UNVERIFIED and vary by TD build, setting expectations.

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