Skip to main content
Glama
Sign In
Houdini MCP

Houdini MCP

by beatreichenbach
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

set_render_settings

Configure render parameters on a Houdini ROP node by specifying the node path and optional settings, enabling controlled render setup.

Instructions

Set render parameters on a ROP node.

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

Input Schema

NameRequiredDescriptionDefault
settingsNo
node_pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full behavioral burden and says nothing about mutation semantics: whether the supplied settings replace or merge with existing render parameters, whether the change persists or is undoable, or what is returned. For a write operation this is a substantial gap.

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 short sentence with no filler and the verb and target front-loaded. It is efficient, though the brevity is achieved by omitting content rather than by tight editing.

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 an opaque nested settings object, no annotations, no output schema, and zero schema descriptions, the definition is too thin to guide correct invocation. At minimum it should describe the settings payload shape and the effect on existing values.

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%, so nothing documents what 'settings' (a free-form object with additionalProperties) should contain or what a valid 'node_path' looks like. The phrase 'render parameters' hints at the settings payload but adds essentially no usable detail beyond the parameter names.

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 names a specific verb and resource ('Set render parameters') plus a target ('ROP node'), so the operation is identifiable. However, it gives no indication of how this differs from the sibling 'get_render_settings' or from generic parameter setters, leaving an agent to infer the distinction 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 guidance on when to use this tool versus alternatives such as 'set_parameter' or 'set_parameters', nor on when not to. The only implied context is that a ROP node must exist, which the agent must deduce.

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