Skip to main content
Glama

render_node_network

Capture a screenshot of a Houdini node's network editor view by specifying the node path and optional output image path.

Instructions

Capture a screenshot of a node's network editor view.

Args: node_path: Node path to focus on. output_path: Image file path; variables ($JOB) are expanded. Default: a new PNG in the temp dir.

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": {
      "node_path": "<node_path>"
    },
    "name": "render_node_network"
  }
}

Input Schema

NameRequiredDescriptionDefault
node_pathYes
output_pathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv2.24.1
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / output_path / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • addedInput schema / properties / output_path / default
      Added value: +null
    • removedInput schema / properties / output_path / type
      Removed value: -"string"
    • changedInput schema / required
      Previous value: -[
      -  "node_path",
      -  "output_path"
      -]New value: +[
      +  "node_path"
      +]
  2. First observedv0.1.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 disclosure burden. It usefully reveals that the tool writes an image file, that $JOB variables are expanded, and that the default target is a new PNG in the temp dir. It does not say whether the file is returned, the path returned, or whether the node must be open/focused in the editor, leaving real behavioral gaps for a side-effecting tool.

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 behavior is front-loaded in one sentence, followed by a compact Args block that documents each parameter. No filler sentences, though the Args formatting is somewhat verbose relative to how little schema detail it adds.

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?

This is a simple two-parameter tool with no output schema and no annotations. The description covers purpose, both parameters, the default output behavior, and variable expansion, which is sufficient for an agent to invoke it correctly; the only omission, the return value, is arguably outside its scope.

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 largely does: node_path is described as the node to focus on, and output_path gains meaning absent from the schema, namely $JOB variable expansion and the default new-PNG-in-temp-dir behavior. It stops short of giving path-format examples or stating what happens if the path already exists.

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?

The description opens with a specific verb and resource: "Capture a screenshot of a node's network editor view." This is concrete enough to distinguish it from generic rendering siblings, but it never names related tools like capture_network_editor or render_viewport, so the agent must infer the boundary from the name alone.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, and no alternatives are named. The agent gets no help deciding between this tool and the sibling capture_network_editor for a similar screenshot task.

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

Deploy Server

Other Tools