Skip to main content
Glama
Sign In
Houdini MCP

Houdini MCP

by beatreichenbach
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

setup_render

Configure a Houdini render with a camera, ROP node, renderer, resolution, samples, and output path to produce renders from a consistent setup.

Instructions

Set up a render configuration with camera and ROP node.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "setup_render"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNorender1
cameraNo
samplesNo
rendererNokarma
resolutionNo
output_pathNo$HIP/render/output.$F4.exr

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/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 burden of behavioral disclosure and largely fails: it does not say whether nodes are created or modified, whether existing render settings are overwritten, what permissions or prerequisites exist, or what the result is. 'Set up' implies mutation but nothing about reversibility, side effects, or defaults is stated.

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?

The single sentence is front-loaded and free of padding, but its brevity reflects under-specification rather than efficiency. There is no structure to separate what is created from what is configurable.

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?

With six optional parameters, zero schema descriptions, no annotations, and no output schema, this definition leaves an agent without the information needed to call it correctly or predict its effects. The brief mention of camera and ROP is the only substantive content.

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 six parameters, and the description only gestures at one of them ('camera') while 'ROP node' does not even map to a parameter. Nothing explains what samples, renderer, resolution, output_path, or name mean or what valid values look like, so the schema gap is not compensated.

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 gives a specific verb and resource ('Set up a render configuration') and names two artifacts involved (camera and ROP node), so the agent knows it is a scene-setup operation. It does not differentiate itself from siblings like create_render_node, set_render_settings, or setup_flip_sim, which keeps it from a 5.

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 statement of when to use this tool, when not to, or which sibling to prefer (e.g., create_render_node vs. set_render_settings). The agent must infer its place in the workflow from the name alone.

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