Skip to main content
Glama

load_scene

Open a Houdini hip file or merge specific nodes into the current scene, restoring set variables and reporting load warnings, conflicts, and merged nodes.

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; $JOB, $HIP and other variables are expanded. 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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "file_path": "<file_path>"
    },
    "name": "load_scene"
  }
}

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.2/5.0
Behavior4/5

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

With no annotations supplied, the description carries the burden and does substantial work: it discloses conflict resolution semantics (rename vs. in-place overwrite), that node paths bring their contents, that $JOB/$HIP are expanded, and the non-obvious side effect that `set -g` variables from the current scene are preserved and reported in `globals_restored`. It omits prerequisites such as requiring a live Houdini connection or how failures surface outside of missing-asset warnings.

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 purpose, then results, then an Args block that maps cleanly to the schema. Some density in the globals_restored/globals_added sentence makes it a heavier read than needed, but every clause conveys distinct behavior rather than filler.

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

Completeness4/5

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

There is no output schema, so describing the returned fields (warnings, merged_nodes, conflicts, not_found_in_file, globals_restored, globals_added) is essential and done well. For a destructive-by-nature scene-replacing operation with zero annotations, a sentence on connection requirements or irreversibility of the non-merge mode would close the remaining gap.

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%, yet the description documents every one of the four parameters with meaning the schema lacks: file_path's variable expansion, merge's replace-vs-additive semantics, node_paths being absolute and content-inclusive with an 'everything' default, and overwrite_on_conflict's rename alternative. Nothing is left for the agent to guess.

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 opening sentence gives a precise verb and resource ('Open a Houdini hip file') and immediately covers the two modes (open vs. merge, whole file vs. named nodes), which clearly separates it from save_scene/new_scene/get_scene_info. It stops short of naming any sibling or stating which one to pick instead, so it lands just under a 5.

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?

Usage context for the optional parameters is explicit: merge switches from replace to additive, node_paths only applies 'with merge' and defaults to everything, overwrite_on_conflict only applies 'with merge'. There are no exclusions or named alternatives (e.g., when to start a new scene rather than load a file), so it is clear context without routing guidance.

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