Skip to main content
Glama
Sign In
Houdini MCP

Houdini MCP

by beatreichenbach
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

start_render

Run any Houdini render or file-writing node, optionally specifying frame range, overrides, and background execution.

Instructions

Execute any node that renders or writes files.

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": "start_render"
  }
}

Input Schema

NameRequiredDescriptionDefault
node_pathYes
overridesNo
backgroundNo
frame_rangeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.2/5.0
Behavior1/5

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

No annotations exist, so the description carries the full behavioral burden and it discloses almost nothing. It does not say whether the call blocks until completion, how the 'background' flag changes behavior, what files or paths get written, whether existing output is overwritten, or what happens with frame ranges. 'Writes files' is the only hint of a side effect for what is clearly a consequential operation.

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

Conciseness3/5

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

It is one short, front-loaded sentence with no filler, but the brevity is under-specification rather than economy. The single sentence has room to state blocking behavior and the node_path requirement without becoming bloated.

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 four-parameter execution tool with no annotations and no output schema, an agent needs to know blocking/async semantics, what gets written, and what the params mean. None of that is present, leaving the definition inadequate relative to the tool's complexity.

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, and the description compensates almost not at all. Only 'node' loosely maps to node_path; overrides, background, and frame_range — including expected shapes and defaults — receive no explanation anywhere.

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

Purpose3/5

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

The description gives a verb ('Execute') and a rough resource class ('any node that renders or writes files'), but 'any node' is vague and it never names what a node path is or which render-related siblings it supersedes. An agent can guess it kicks off a render/write, but cannot confidently separate it from render_viewport, render_node_network, or setup_render.

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: nothing about when to prefer this over render_viewport/render_node_network, when to poll progress with get_render_progress, or whether setup_render must run first. Usage can only be inferred from the phrase 'renders or writes files'.

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