Skip to main content
Glama
Sign In
Houdini MCP

Houdini MCP

by beatreichenbach
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

find_error_nodes

Locate all Houdini nodes with errors or warnings in the scene or a specified root path so you can troubleshoot issues quickly.

Instructions

Find all nodes with errors or warnings in the scene.

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

Input Schema

NameRequiredDescriptionDefault
root_pathNo/

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden. It does not say whether the operation is read-only, whether it triggers cooking or evaluation of nodes to discover errors, how expensive a full-scene scan is, or what the results contain beyond the node list.

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 front-loaded sentence with no filler, appropriate for the tool's simplicity. It is efficient, though it omits the scoping parameter entirely.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple and read-only in nature, so a one-line description is close to adequate. However, the undocumented root_path and the absence of any information on result shape leave gaps for an agent that needs to scope and interpret the search.

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 coverage is 0% and there is one parameter, root_path, which the description never mentions. It does not explain that the search is scoped to a subtree or that '/' means the whole scene by default, so the agent gets no guidance beyond the bare schema field.

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: 'find' plus 'nodes with errors or warnings.' An agent can distinguish this from find_nodes and find_expensive_nodes because the filtering criterion (error/warning state) is explicit.

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 about when to use this instead of find_nodes or find_expensive_nodes, nor any prerequisite or exclusion. Usage is only implied by the tool's diagnostics framing.

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