Skip to main content
Glama
Sign In
Houdini MCP

Houdini MCP

by beatreichenbach
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

set_viewport_renderer

Set the Hydra rendering delegate for a viewport to control live preview output in Houdini.

Instructions

Set the viewport's Hydra rendering delegate for live preview.

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

Input Schema

NameRequiredDescriptionDefault
rendererYes
pane_nameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It says the tool sets a Hydra rendering delegate for live preview, but does not explain persistence, valid renderer values, what happens to an existing delegate, how pane_name affects scope, or whether the change is reversible.

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 description is a single, front-loaded sentence with no filler or redundancy. Its brevity is efficient, though it leaves important details unstated.

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 two parameters, zero schema description coverage, no annotations, and no output schema, the definition is too thin. An agent would lack critical information about valid renderer values, pane targeting, and behavioral side effects.

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 the description must compensate. It clarifies that 'renderer' refers to a Hydra rendering delegate, but gives no valid values or format, and it completely omits the optional 'pane_name' parameter and its effect on which viewport is targeted.

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 states a specific verb and resource: 'Set the viewport's Hydra rendering delegate,' making the tool's action clear. It distinguishes itself implicitly from siblings like set_viewport_camera or set_viewport_display, though it does not explicitly name alternatives.

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

Usage Guidelines3/5

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

'For live preview' provides a contextual hint about when the tool is relevant, but there is no explicit guidance on when to use it versus render_viewport, set_viewport_display, or other viewport tools. No prerequisites or exclusions are stated.

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