Skip to main content
Glama

save_scene

Persist the current Houdini scene to disk, optionally specifying a destination path with variables expanded. Use it to record scene changes or save the hip file to a new location.

Instructions

Save the current Houdini scene to disk.

Args: file_path: Destination path; defaults to the current hip file. $JOB, $HIP and other variables are expanded.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "save_scene"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_pathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.24.1
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it omits the traits most relevant to a disk write: whether the target file is overwritten, what happens when the path is invalid or unwritable, whether the save is versioned or atomic, and whether any confirmation or result is returned. Only the default-path and variable-expansion behavior is disclosed.

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?

One front-loaded sentence states the action, followed by a compact Args block that exists only because the schema has no descriptions. There is no filler or restatement.

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

Completeness3/5

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

The tool is simple: one optional parameter and no output schema and no annotations. The description covers the action and the parameter, but it says nothing about overwrite semantics or failure behavior, which matter for a persistent write. It is adequate but has a clear gap.

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 descriptions cover 0% of the parameters, so the description must compensate. It does so well for the single parameter: it gives the destination meaning, the default to the current hip file, and expands $JOB and $HIP variables, none of which the schema conveys. It does not cover the path format or relative-path handling, which keeps it from a 5.

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 description gives a specific verb and resource ("Save the current Houdini scene to disk"), which marks it distinct from the other scene tools I can see, such as get_scene_info, load_scene and new_scene. It never names any of those tools explicitly, so it is a clear purpose without explicit sibling differentiation.

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 verb "save" implies its usage, but the description never says when to save to the current file versus a new path, nor when to use a related tool such as load_scene or new_scene. The only hint is that file_path silently defaults to the current hip file, which lets the agent infer that omitting it means an in-place save.

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