Skip to main content
Glama

Get operator runtime state

get_node_state_runtime
Read-only

Diagnose why a specific operator is slow or black by viewing its runtime telemetry: cook time, GPU memory, resolution, errors, and more.

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

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

Annotations already provide readOnlyHint=true and destructiveHint=false, and the description reinforces this with 'Read-only'. It adds valuable context beyond annotations: return shape, UNVERIFIED attribute names that vary by TD build, and the `extra` map for live confirmation. No contradiction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is information-dense but every sentence earns its place: scope and fields, sibling context, and return/caveat details. It is front-loaded with 'Read-only' and well-structured, though slightly long for the minimalist ideal.

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?

For a read-only telemetry tool with two simple parameters and strong annotation coverage, this description is complete. It covers what fields are returned, the diagnostic use case, safety, and the important UNVERIFIED attribute caveat. The Info CHOP fallback behavior is also documented in the schema.

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?

Schema description coverage is 100% for both parameters, so baseline 3 applies. The description mentions include_info_chop's purpose at a high level but adds no syntax or constraints beyond what the schema already states. path is straightforward and needs no extra explanation.

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?

Description opens with 'Read-only: inspect a single operator's runtime telemetry', giving a specific verb and resource, then lists concrete fields. It explicitly differentiates from sibling get_td_performance by noting the per-op vs network-aggregate scope.

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?

It clearly states the diagnostic context ('why is it black / why is it slow') and names get_td_performance as the network-level aggregation tool. However, it presents the relationship as 'complements' rather than an explicit 'use X instead when Y', so it lacks a firm exclusion rule.

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