Skip to main content
Glama

uninstall_hda

Removes an installed HDA from the current Houdini session using a file path with $JOB variables expanded.

Instructions

Uninstall an HDA file from the current session.

Args: ctx: MCP context. file_path: HDA file path; variables ($JOB) are expanded.

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

Input Schema

NameRequiredDescriptionDefault
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.1/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. 'Uninstall' is a removal operation, yet the description never states whether the on-disk file is deleted (implied not, by 'from the current session'), whether running node instances are broken, whether the action is reversible, or what errors occur when the path is not installed.

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 well front-loaded and short, but the docstring artifacts ('Args:', 'ctx: MCP context.') add no value for an agent choosing a tool. Roughly half the text is scaffolding rather than signal.

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?

For a destructive, unannotated tool with no output schema, the definition is thin: it omits post-conditions (what state the session is left in), failure modes (path not installed), and effects on currently instantiated nodes. Only the variable-expansion detail is supplied.

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 coverage is 0% (the single parameter is just 'File Path'), so the description must compensate, and it does: it clarifies this is an HDA file path and that variables such as $JOB are expanded before use. That is meaningful semantics the schema does not convey. The 'ctx' arg note is boilerplate but harmless.

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?

States a specific verb and resource ('Uninstall an HDA file') plus a scope ('from the current session'), which reads clearly against siblings like install_hda and reload_hda. It stops short of explicitly contrasting with those siblings, so it lands at 4 rather than 5.

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?

'From the current session' implies the tool operates on loaded definitions rather than files on disk, which hints at when it applies. However, there is no explicit when-to-use/when-not-to-use guidance, no mention of preferring reload_hda for refreshing an already-loaded HDA, and no prerequisites such as requiring the HDA to be installed first.

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