Skip to main content
Glama
healkeiser

fxhoudinimcp

by healkeiser
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

load_scene

Load a Houdini hip file into the current scene, or merge selected nodes from it, with options to overwrite conflicts and receive warnings.

Instructions

Open a Houdini hip file, or merge it — or named nodes from it — into the current scene.

Load warnings (missing assets and the like) come back in warnings. A merge reports what arrived: merged_nodes, conflicts (a node that already exists is merged under a new name, or overwritten in place with overwrite_on_conflict=True) and not_found_in_file. node_paths are absolute (/obj/building_v3) and bring their contents.

Args: file_path: Path to the hip file to open. merge: Merge into the current scene instead of replacing it. node_paths: With merge, the absolute node paths to merge; default everything. overwrite_on_conflict: With merge, overwrite same-named nodes instead of renaming the merged copy.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mergeNo
file_pathYes
node_pathsNo
overwrite_on_conflictNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.18.0
    • addedInput schema / properties / node_paths
      Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Node Paths"
+}
    • addedInput schema / properties / overwrite_on_conflict
      Added value: +{
+  "default": false,
+  "title": "Overwrite On Conflict",
+  "type": "boolean"
+}
  2. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and covers it well: it discloses that opening replaces the scene, that merges report merged_nodes/conflicts/not_found_in_file, how conflicts are resolved via overwrite_on_conflict, and that node_paths are absolute and bring their contents. This gives an agent a clear picture of side effects and return data.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured and front-loaded with the primary purpose, followed by return/behavioral details in prose, then a clear Args list. Every sentence contributes useful information without redundancy or padding.

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?

For a tool with no annotations, no output schema, and four interdependent parameters, this description is complete: it documents the operation modes, parameter semantics, conflict behavior, and return values. An agent has everything needed to call the tool correctly.

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 coverage is 0%, so the description must explain all parameters, and it does thoroughly: file_path, merge behavior, node_paths defaulting to everything, and overwrite_on_conflict semantics. It adds meaning far beyond the bare schema field names.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description uses a specific verb ('Open') and resource ('Houdini hip file'), then immediately clarifies the two modes: replace the current scene or merge into it. It distinguishes itself from related tools like new_scene, save_scene, and import_file by explicitly stating the replace-vs-merge distinction.

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?

The description gives clear context on when to use load_scene in either mode, including the effect of merge and node_paths. It does not explicitly name sibling alternatives or state when not to use this tool, but the behavioral context is sufficient for an agent to select it appropriately.

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