Skip to main content
Glama

nodes

Inspect a clip’s node graph or set one node’s enabled state and cache mode, targeting clips, timelines, or groups.

Instructions

Inspect a clip's node graph (count, labels, tools used, LUTs, cache mode) or change one node: enabled, cache (auto | enabled | disabled). Target: clip ref, 'timeline' or 'group::pre|post'.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "clip": "<clip>"
    },
    "name": "nodes"
  }
}

Input Schema

NameRequiredDescriptionDefault
clipYes
nodeNo
cacheNo
layerNo
enabledNo
reset_node_colorsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It usefully discloses that the tool both reads and mutates, and enumerates the cache values (auto | enabled | disabled), but says nothing about authorization, whether toggling cache or enabled persists across renders, or reversibility.

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?

Two dense, front-loaded sentences with no filler; the read path, write path, and target syntax are each stated once. The parenthetical facet list and inline enum are packed, but every element carries information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no annotations, no output schema, and six parameters, more disclosure is needed. The description omits what the inspect mode returns, how layer scopes the operation, and what reset_node_colors does, so an agent cannot call this correctly in every mode.

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 description coverage is 0%, so the description must compensate, and it does for most parameters: clip target and accepted target forms, the singular node being modified, enabled, and cache with its enum values. It omits layer and reset_node_colors entirely, leaving those two parameters unexplained anywhere.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Inspect a clip's node graph' with the inspected facets enumerated (count, labels, tools used, LUTs, cache mode), plus a second mutation mode. The dual inspect/change nature is clear, but there is no differentiation from related siblings such as fusion_comps or color_groups.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implied usage: inspect the graph, or change exactly one node's enabled/cache state, with valid target forms given ('clip ref', 'timeline', 'group:<name>:pre|post'). It never states when to pick this over alternatives or what preconditions must hold before mutating a node.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.