HoudiniMCP

Overview Schema Source Related Servers Discussions Admin

scene_file

Destructive

Read, save, load, undo, or redo Houdini scene files. Check unsaved work before risky changes, then save or step through undo history.

Instructions

Read, save or load the scene file, or step its undo history.

Use "save" before a change that is hard to undo, and use "info" to learn
whether the session holds work that is not saved.

mode:
    "info" — the file name, the frame range, the counts, and whether the
             session has changes that are not saved.
    "save" — save to `path`, or over the open file when `path` is empty.
    "load" — open the .hip file at `path`. Everything in the session goes
             away, and the undo history with it.
    "undo" — undo `count` steps. Each call of a tool that changes the
             scene is one step. A batch is one step, except a batch with a
             step that waits (capture, render): there each step is one.
             Returns the labels it undid and the next ones.
    "redo" — redo `count` steps.

Returns JSON.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`mode`	No	One of "info", "save", "load", "undo", "redo".	info
`path`	No	save: the file to write; empty saves over the open file. load: the .hip file to open.
`count`	No	undo and redo: how many steps.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields changedv0.7.3Oct 4, 2026

addedInput schema / properties / count

Added value: +{
+  "default": 1,
+  "description": "undo and redo: how many steps.",
+  "type": "integer"
+}

removedInput schema / properties / mode / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / mode / description

Added value: +"One of \"info\", \"save\", \"load\", \"undo\", \"redo\"."

removedInput schema / properties / mode / title
```
Removed value: -"Mode"
```
addedInput schema / properties / mode / type
```
Added value: +"string"
```

removedInput schema / properties / path / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

removedInput schema / properties / path / default
```
Removed value: -null
```

addedInput schema / properties / path / description

Added value: +"save: the file to write; empty saves over the open file. load: the .hip file to open."

removedInput schema / properties / path / title
```
Removed value: -"Path"
```
addedInput schema / properties / path / type
```
Added value: +"string"
```
removedInput schema / title
```
Removed value: -"toolArguments"
```

Addedv0.1.1Oct 4, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Goes well beyond the annotations (destructiveHint=true, readOnlyHint=false) by spelling out that 'load' discards everything in the session and the undo history, and by defining what constitutes an undo step (one scene-changing tool call, a batch as one step except when it waits on capture/render). This is exactly the behavioral detail annotations cannot convey.

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-loads the one-line purpose, then a usage hint, then a clean mode list. The undo-step paragraph is somewhat verbose but each sentence carries operational meaning, so little is wasted.

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?

Output schema exists so return values need no elaboration, and the description still notes 'Returns JSON' plus which mode returns undone labels. Destructive 'load' behavior and undo semantics are disclosed, leaving no gap for correct invocation.

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

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% (baseline 3), but the description adds real meaning: it explains what each mode does with `path` (save over open file when empty, open .hip on load) and what `count` means per undo step. This exceeds the schema's terse per-parameter notes.

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 set and resource (read/save/load the scene file, step its undo history) and enumerates all five modes with their exact effect. An agent can distinguish this from siblings like scene_overview or session without opening the 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?

Gives explicit when-to-use guidance for two modes: 'save' before a hard-to-undo change, and 'info' to check for unsaved work. It does not name alternative tools or state when NOT to use this one (e.g. versus scene_overview), so it stops short of full 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