Skip to main content
Glama
healkeiser

fxhoudinimcp

by healkeiser
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

verify_network

Inspect every node in a Houdini network for errors, warnings, bypassed flags, and display geometry; use it after building or edits to fix problems before finishing.

Instructions

Inspect every node in a network at once — errors, warnings, flags, and the display node's cooked geometry counts.

Call this after building or modifying a network, the way an artist middle-clicks nodes: if healthy is false or error_nodes is non-empty, fix those nodes before telling the user anything is done. Each node lists errors, warnings, bypassed and display only when it has them; absent means none. For a LOP network the evidence is the stage (prims, cameras, lights, gprims without a material), for a COP network the image layer (resolution, channel ranges).

A node's errors are its LAST cook's verdict. A node that nothing has cooked since its cause was fixed is reported stale and listed in stale_error_nodes; pass force_cook=True to recook before judging. The default cooks only the display node, so a heavy scene is left alone.

Args: parent_path: Network to verify (e.g. "/obj/geo1"). force_cook: Cook the display node with force and recook every node that has errors, so the verdict is about the network as it is now.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
force_cookNo
parent_pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.24.1
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / force_cook
      Added value: +{
+  "default": false,
+  "title": "Force Cook",
+  "type": "boolean"
+}
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

No annotations exist, so the description carries full burden and does so richly: absent fields mean none, errors reflect the LAST cook, uncooked nodes are reported stale and listed in stale_error_nodes, and the default only cooks the display node so heavy scenes are left alone. This is exactly the behavioral context an agent needs.

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?

Front-loaded with the core purpose before any caveats, and most sentences carry real information. It is somewhat long and the force_cook explanation slightly restates the earlier display-node-cook point, but nothing is filler.

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

Completeness5/5

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

With no output schema, the description must convey return shape, and it does: healthy, error_nodes, stale_error_nodes, per-node errors/warnings/bypassed/display, plus LOP/COP evidence fields. An agent can both invoke it and interpret results without further documentation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/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, and it does: parent_path is given a concrete form ('/obj/geo1'), and force_cook is explained not just as a flag but as recooking the display node plus every erroring node so the verdict reflects the network's current state.

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?

States a specific verb and scope — 'inspect every node in a network at once' — and enumerates what is inspected (errors, warnings, flags, cooked geometry counts). This distinguishes it in spirit from narrower siblings like find_error_nodes or get_node_errors_detailed, though it never names an alternative explicitly.

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

Usage Guidelines4/5

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

Gives clear usage context: 'Call this after building or modifying a network... if healthy is false or error_nodes is non-empty, fix those nodes before telling the user anything is done.' The when-to-use is explicit, but no when-NOT-to-use or named alternative (e.g. get_node_errors_detailed, find_error_nodes) is offered.

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