Skip to main content
Glama

export_file

Export a Houdini node’s output to a specified file path, optionally across a frame range, and report whether files were actually written or changed.

Instructions

Export a node's output to a file on disk, and report whether it landed.

SOPs are saved directly, LOPs export their USD stage, and a /out ROP is pointed at file_path and executed (its own output path is restored afterwards). Reports wrote_files, so success: True means a file appeared or changed -- not merely that the call returned. A frame_range writes name.0001.ext per frame and leaves the playbar where it was. A missing directory is created, as a ROP or a USD export does.

Args: node_path: Path to the node to export. file_path: Destination file path; variables ($JOB) are expanded. For a ROP this overrides its output parameter for the duration of the export. frame_range: Frame range as [start, end] or [start, end, step].

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": {
      "node_path": "<node_path>",
      "file_path": "<file_path>"
    },
    "name": "export_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_pathYes
node_pathYes
frame_rangeNo

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

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full disclosure burden and does so well: it explains side effects (ROP output path restored afterwards), result semantics ('success: True means a file appeared or changed'), frame_range naming ('name.0001.ext'), playbar preservation, and implicit directory creation. Gaps remain on overwrite behavior and failure signaling beyond wrote_files, keeping it below a 5.

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?

Behavior is front-loaded in the first paragraph, structural detail follows, and the Args block adds only information not already conveyed in prose. No filler sentences; each line (e.g. 'leaves the playbar where it was') carries operational meaning.

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?

For a 3-parameter mutation tool with no annotations and no output schema, the description covers dispatch behavior, side effects, result interpretation, and directory creation. What is missing is error/failure behavior and whether existing destination files are clobbered.

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 description coverage is 0%, so the description must compensate, and it largely does: file_path documents $JOB variable expansion and the ROP output-parameter override, and frame_range documents both the [start, end, step] form and the per-frame filename it produces. node_path is left as a bare one-liner, so a small gap persists.

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?

Opens with a specific verb+resource and scope: 'Export a node's output to a file on disk, and report whether it landed.' The following sentence distinguishes the three node classes (SOP/LOP//out ROP) it dispatches on, so an agent knows exactly what the tool does before 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 clear usage context by naming the node types it handles and the differing mechanics for each ('SOPs are saved directly, LOPs export their USD stage, and a /out ROP is pointed at file_path'). It stops short of explicit exclusions or pointing to an alternative sibling (e.g. export_chop_to_parm or import_file).

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