Skip to main content
Glama
Sign In
Houdini MCP

Houdini MCP

by beatreichenbach
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

create_render_node

Creates a new render (ROP) node in Houdini’s /out network, letting you set the renderer, camera, output path, and node name for render setup.

Instructions

Create a new render (ROP) node in /out.

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": {
      "renderer": "<renderer>"
    },
    "name": "create_render_node"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
cameraNo
rendererYes
output_pathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and largely does not meet it. It does disclose the creation location (/out), which is useful, but says nothing about permission/session requirements, behavior on invalid renderer strings, duplicate name handling, or what is returned (node path/object).

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?

A single front-loaded sentence with zero filler; the verb and target resource come first. Its brevity is efficient rather than bloated, though the same brevity is what leaves the behavioral and parameter gaps.

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

Completeness2/5

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

For a mutation tool with no annotations, no output schema, and four fully undescribed parameters, this description is under-specified. An agent knows what it creates and where, but not how to populate renderer/camera/output_path or what to expect afterward.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across four parameters, so the description must compensate and does not. The phrase 'in /out' implicitly explains why there is no parent-path parameter, but renderer (required), camera, output_path, and name receive no meaning, format hints, or defaults from the description.

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 (create a render/ROP node) plus the target location (/out), which lets an agent distinguish it from siblings like create_chop_node or create_cop_node by node family. It stops short of explaining how it relates to the generic create_node sibling, so differentiation is implied rather than explicit.

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 guidance, no prerequisite (e.g., scene/session context), and no mention of alternatives such as create_node with a renderer type or setup_render. The only usage signal is the implied one that this is for building a render network.

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