Skip to main content
Glama
healkeiser

fxhoudinimcp

by healkeiser
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

load_scene

Open a Houdini HIP file to replace the current scene, or merge the file or chosen node paths into it while returning warnings and merge conflicts.

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. Changed1 schema field changedv2.24.1
    • addedInput schema / additionalProperties
      Added value: +false
  2. 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"
+}
  3. First observedv0.1.0

TDQS

A4.7/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 does so well: it discloses that load warnings arrive in `warnings`, that a merge replaces vs renames conflicting nodes depending on overwrite_on_conflict, and that node_paths are absolute and pull their contents. This is meaningful side-effect and conflict-handling detail beyond the schema.

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 action, followed by a scannable return-field list and Args block. Every sentence earns its place given the 0% schema coverage, though the prose is slightly verbose.

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?

No output schema exists, but the description names the return fields (warnings, merged_nodes, conflicts, not_found_in_file), so an agent knows what to expect. Combined with full per-parameter docs, nothing needed to call it correctly is missing.

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 its Args block documents all four parameters including the non-obvious interaction between merge, node_paths, and overwrite_on_conflict. It adds real semantics the bare schema does not.

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?

States a specific verb+resource ('Open a Houdini hip file, or merge it — or named nodes from it — into the current scene') and clearly distinguishes open-vs-merge scope. An agent can separate this from siblings like new_scene, save_scene, and import_file without opening a schema.

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?

Explains the two modes precisely and ties each parameter to its condition ('With merge, ...'). It stops short of naming alternatives such as import_file or new_scene, so the when-not guidance is implied rather than explicit.

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