Skip to main content
Glama

edit_hda_interface

Edit an HDA's existing Type Properties interface in one atomic call: insert, remove, hide/show, replace, modify, or move parameters, with validation before writing.

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.

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.

Input Schema

TableJSON 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, the description carries the full burden and does so: atomic copy-then-write semantics ('a failing op changes nothing'), collision checking, the built-in-parameter constraint with the reinstated_by_houdini reply field, and dry_run behavior. This is exactly the behavioral detail an agent needs before mutating an HDA definition.

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?

It is front-loaded (purpose, then the append-only distinction, then the atomicity guarantee, then op grammar) and every block is functional. It is long, but the length is driven by a genuinely complex op grammar with 0% schema coverage; only the parenthetical alias notes feel slightly compressible.

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?

There is no output schema, yet the description surfaces the relevant reply fields (reinstated_by_houdini, stored, instance_expression_errors) and the failure semantics. For a 3-parameter, high-complexity mutation tool with no annotations, nothing material is 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 coverage is 0%, so the description must compensate, and it does: it fully enumerates the op dict grammar (insert/remove/hide/show/replace/modify/move), each op's positional keys, the spec fields, naming variants and aliases, and the meaning of node_path and dry_run. This exceeds what a bare schema would have provided.

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?

The opening sentence states a specific verb (edit), resource (an HDA's EXISTING Type Properties interface), and enumerates the six supported operations. It also explicitly distinguishes itself from the sibling set_hda_interface ('only appends'), so an agent can route between the two without opening a 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?

It names the alternative (set_hda_interface appends; this tool edits existing entries) and states the prerequisite workflow ('Read the interface first with get_parm_template_tree'). The dry_run parameter and the read-first instruction give clear when-to-use and when-to-call-something-else guidance.

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