Skip to main content
Glama
healkeiser

fxhoudinimcp

by healkeiser
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

load_scene

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

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. A merge keeps the scene's set -g variables ($JOB, $POSE) the file would overwrite, named in globals_restored with the file's value and the kept one; variables the file adds are listed in globals_added.

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

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.3/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 richly: it discloses that missing-asset warnings are returned, that a conflict renames or overwrites depending on overwrite_on_conflict, and that scene globals ($JOB, $POSE) are preserved via globals_restored/globals_added. That is exactly the side-effect and conflict-resolution detail a mutation tool 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 action, then behavior, then args — a clean structure with little waste. The output-field narration is dense but each field named (merged_nodes, conflicts, globals_restored) earns its place by describing real behavior.

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, yet the description enumerates the returned fields (warnings, merged_nodes, conflicts, not_found_in_file, globals_restored, globals_added), and it covers mode selection and edge cases. For a mutation tool with no annotations, this is complete enough to call 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 description coverage is 0%, so the description must compensate, and it does: all four parameters get meaning beyond their titles — file_path's target, merge's replace-vs-merge choice, node_paths being absolute paths that bring their contents and defaulting to everything, and overwrite_on_conflict's rename-vs-overwrite behavior.

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 resource plus two distinct modes: 'Open a Houdini hip file, or merge it — or named nodes from it — into the current scene.' This is far more precise than the bare name, but it never names or contrasts with related siblings such as import_file, new_scene, or save_scene, so sibling differentiation is left implicit.

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

Usage Guidelines3/5

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

The Args section explains when to use merge vs. replace, node_paths' default, and overwrite_on_conflict's effect — that is solid within-tool guidance. However there is no tool-level 'use this instead of X' guidance, so an agent gets only implied usage relative to alternatives.

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