Skip to main content
Glama
Sign In
Houdini MCP

Houdini MCP

by beatreichenbach
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

install_hda

Installs an HDA file into the current Houdini session. Load custom digital assets by specifying the file path, with an optional force flag.

Instructions

Install an HDA file into the current session.

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. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It states that installation targets the current session, but does not disclose side effects, overwrite behavior, persistence, permissions, failure modes, or what the force flag changes. That leaves important behavioral traits undocumented for a mutation-style tool.

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?

The definition is a single front-loaded sentence with no wasted wording. It is efficient and easy to scan, though its brevity contributes to the completeness gaps rather than being ideal for this tool. The structure itself is clean.

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

Completeness2/5

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

This is an installation tool with two parameters, no annotations, no output schema, and no parameter descriptions. The description does not explain the force flag, session scope persistence, side effects, or expected outcome. It is therefore not complete enough for an agent to invoke it confidently beyond the basic action.

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

Parameters2/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 for both parameters. It implies that file_path refers to an HDA file, but provides no format, path, or validation details. The force parameter is not mentioned at all, leaving a required behavioral input unexplained.

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 states a specific verb and resource: 'Install an HDA file'. It also clarifies the destination scope as 'the current session', which helps distinguish installation from HDA creation or editing. It does not explicitly differentiate from siblings such as create_hda or reload_hda, so it falls short of a 5.

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?

The description provides no explicit when-to-use guidance, prerequisites, or alternatives. It implies that this tool installs an HDA file into the current session, but does not say when to choose it over create_hda, reload_hda, or uninstall_hda. The only usage context is the broad phrase 'into the current session'.

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