Retrieve available Hydra render delegates for a Houdini LOP Scene Viewer and identify the active one. Use this to inspect renderer options in a live Houdini session.
List Hydra delegates on the LOP Scene Viewer and the current one.
| Name | Required | Description | Default |
|---|---|---|---|
| viewer | No |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It reveals only that a 'current' delegate is included, saying nothing about whether the operation is read-only, what requires the viewer to be open, or how multiple delegates are returned.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
One tight sentence with no filler, front-loading the verb and resource. Slightly terse given the unexplained viewer parameter, but structurally clean.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists, so the return format need not be described. However, the undocumented viewer parameter and the absence of any behavioral or usage context leave gaps for correctly invoking the tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The single 'viewer' parameter has 0% schema description coverage and is not mentioned in the description at all, so the agent cannot tell what value it expects (name, path, index?) or what omitting it defaults to.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb 'List' plus resource 'Hydra delegates' scoped to the LOP Scene Viewer, and notes it also returns the current delegate. Implicitly contrasted with the sibling set_hydra_renderer, but that alternative is never named.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to call this versus set_hydra_renderer, restart_renderer, or set_viewport_renderer. The agent is left to infer that this is the read counterpart to the setters.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.