Skip to main content
Glama

import_file

Imports geometry, USD, or Alembic files into a Houdini scene; expands $JOB variables and creates the node under a chosen parent path with an optional name.

Instructions

Import a geometry, USD, or Alembic file into the scene.

Args: file_path: Path to the file to import; variables ($JOB) are expanded. parent_path: Network path for the import node. node_name: Name for the created node.

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": "import_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_pathYes
node_nameNo
parent_pathNo/obj

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

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

With no annotations, the description carries the full behavioral burden. It discloses supported formats and that $JOB variables are expanded, but does not state whether existing nodes are overwritten, whether the operation is undoable, what errors may occur, or what side effects importing has on the scene.

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?

The description is front-loaded with the core action and then uses a compact Args block for parameters. There is no redundant wording, and every line contributes information.

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?

There is no output schema and no annotations, so the description should ideally cover import behavior more fully (e.g., Alembic frame ranges, USD variant selection, node creation semantics). It is minimally adequate for a three-parameter import tool but leaves behavioral gaps.

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. It meaningfully explains all three parameters: file_path (including variable expansion), parent_path (network path for the import node), and node_name (name for the created node). This adds real meaning beyond the schema titles.

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 uses a specific verb ('Import') and resource ('geometry, USD, or Alembic file') with a clear destination ('into the scene'). It is distinguishable from the sibling export_file, although it does not explicitly route against other potential import-adjacent tools.

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

Usage Guidelines2/5

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

No guidance is given about when to use this tool versus alternatives, no prerequisites (e.g., connected Houdini session), and no exclusions. The Args section documents parameters but does not address usage context.

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