Skip to main content
Glama

edit_hda_interface

Edit an HDA's existing Type Properties parameter interface atomically: insert, remove, hide, replace, modify, or move parameters, with validation before a single write.

Instructions

Edit an HDA's EXISTING Type Properties interface in one atomic call: insert at a position, remove, hide/show, replace, modify, move.

set_hda_interface only appends. Every op here works on the definition's parameter group; all ops are applied to a copy, the result is checked for component-name collisions, and it is written once — a failing op changes nothing. Read the interface first with get_parm_template_tree.

Ops (dicts, applied in order): {"op": "insert", "spec": {...}, "after": name | "before": name | "in_folder": label or [labels]} — omit the position to append. spec is a set_hda_interface spec, plus types button (with "callback", Python by default), separator, label, vector, color, file, oppath; and fields naming_scheme (base1|xyzw|rgba|minmax| startend|uvw), default_expression (+ default_expression_language), hidden, join_with_next, callback, tags; folder_type "multiparm" for a multiparm block (children named "item#"). {"op": "remove", "name": name_or_folder_label} {"op": "hide" | "show", "name": ...} {"op": "replace", "name": ..., "spec": {...}} {"op": "modify", "name": ..., <label | help | default | default_expression | default_expression_language | min | max | min_strict | max_strict | hide_when | disable_when ("" clears) | hidden | join_with_next | menu_items | callback | naming_scheme | new_name | tags>} ("rename", "set_conditional", "set_default" are aliases) {"op": "move", "name": ..., "after" | "before" | "in_folder": ...}

Names are template names (t, not tx; stud_count); folders are addressed by label ("Controls"). Built-in parameters of the node type (an Object's Transform) cannot be removed — Houdini re-adds them at the top level and the reply says so in reinstated_by_houdini; hide them.

default_expression_language is "hscript" (Houdini's default) or "python"; given alone in a modify, it changes the language of the expression already there. stored reads both back, and instance_expression_errors names a default expression that does not evaluate on the instance. stored carries each template's help, a button's callback and a label's column_labels, and help_not_stored names one whose help the definition did not keep.

Args: ctx: MCP context. node_path: An instance of the HDA whose definition is edited. ops: Operations, in order. dry_run: Validate and report the plan without writing.

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>",
      "ops": "<ops>"
    },
    "name": "edit_hda_interface"
  }
}

Input Schema

NameRequiredDescriptionDefault
opsYes
dry_runNo
node_pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.24.1
    • addedInput schema / additionalProperties
      Added value: +false
  2. Addedv2.18.0

TDQS

A4.9/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full burden and does so: it discloses all-or-nothing atomicity ('all ops are applied to a copy, the result is checked for component-name collisions, and it is written once — a failing op changes nothing'), the non-obvious Houdini behavior that built-in parameters are reinstated at top level and must be hidden instead, and the dry_run validation mode. Remaining minor gap is permissions/locking, which is minor for a local-session 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?

Front-loaded with purpose and the sibling contrast, then organized into a scannable op list and args. It is dense rather than padded, but the trailing paragraph mixes return-value details ('stored', 'instance_expression_errors', 'help_not_stored') into what is nominally a behavior narrative, adding some sprawl to an already long description.

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

Completeness5/5

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

For a complex multi-op mutation tool with no annotations and no output schema, the description covers atomicity, failure semantics, name-vs-label addressing, built-in parameter handling, dry_run, and names several response keys that signal partial conditions. Nothing an agent needs in order to call it correctly appears to be missing.

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

Parameters5/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 does: ops is documented op-by-op with required keys, positional selectors ('after'/'before'/'in_folder', omit to append), the extended spec fields per parameter type, and the modify field set including the '"" clears' convention and aliases. node_path is clarified as 'An instance of the HDA whose definition is edited' (not the definition itself), and dry_run as 'Validate and report the plan without writing.'

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?

States a specific verb and resource ('Edit an HDA's EXISTING Type Properties interface') and immediately enumerates the six operations supported (insert, remove, hide/show, replace, modify, move). It also explicitly separates itself from the nearest sibling by noting 'set_hda_interface only appends,' so an agent can pick between them without opening either schema.

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

Usage Guidelines5/5

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

Names the alternative tool explicitly and gives the discriminating condition ('only appends'), and it prescribes a prerequisite step: 'Read the interface first with get_parm_template_tree.' The 'EXISTING' emphasis and the note about built-in parameters that cannot be removed further constrain when this call is appropriate.

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