Skip to main content
Glama

install_hda

Installs an HDA file into the current Houdini session, expands path variables such as $JOB, and supports forced reinstall when the asset is already loaded.

Instructions

Install an HDA file into the current session.

Args: ctx: MCP context. file_path: HDA file path; variables ($JOB) are expanded. force: Force reinstall even if already loaded.

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

Input Schema

NameRequiredDescriptionDefault
forceNo
file_pathYes

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

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

No annotations, so the description carries the full burden. It does disclose session-scoping and the force-overwrite behavior, but says nothing about what happens when an HDA with the same name is already loaded without force (error, skip, or overwrite), whether the install persists to disk, or what errors look like.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core sentence is front-loaded and efficient, but the Args block leaks an MCP `ctx` entry that is not a schema parameter, which adds noise and could mislead an agent into passing a context argument.

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?

For a two-parameter, no-output-schema tool this is adequate but thin: idempotency, already-loaded behavior, and failure modes are undefined, which matters for a session-mutating install operation.

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% (titles only), so the description must compensate and largely does: it explains `file_path` accepts paths with variables like $JOB expanded, and that `force` reinstalls even if already loaded. Only the path-resolution base and relative-path behavior remain unstated.

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?

Names a specific verb+resource: 'Install an HDA file into the current session.' Clear what it does and that the effect is session-scoped, but no differentiation from apparent siblings like create_hda, reload_hda, or uninstall_hda.

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?

Provides only the conditional for `force` ('even if already loaded'). No guidance on when to use this versus reload_hda or create_hda, and no prerequisites such as a live Houdini connection or a resolved file path.

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