Skip to main content
Glama

create_hda

Convert an existing Houdini subnet node into a reusable HDA file, defining its type name, label, and version.

Instructions

Create a new HDA from an existing subnet node.

A Copernicus subnet's connectors are signed from its own Input/Output parms (inputtype#/outputtype#, labels): a cable output stays Cable. connectors reads them back.

Args: ctx: MCP context. node_path: Subnet node path. hda_file: Destination HDA file path; variables ($JOB) are expanded. type_name: Operator type name. label: Human-readable label. version: Version string.

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>",
      "hda_file": "<hda_file>",
      "type_name": "<type_name>",
      "label": "<label>"
    },
    "name": "create_hda"
  }
}

Input Schema

NameRequiredDescriptionDefault
labelYes
versionNo1.0
hda_fileYes
node_pathYes
type_nameYes

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

C2.9/5.0
Behavior2/5

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

With no annotations at all, the description carries the full burden and only partially meets it. It usefully discloses that $JOB-style variables in hda_file are expanded and that a Copernicus subnet's connectors are signed from its Input/Output parms, but it never says what happens if the destination HDA file already exists, whether the node is modified, what permissions are needed, or what is returned.

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 summary sentence is properly front-loaded, but the Copernicus connector paragraph is tangential to invoking the tool and mentions a `connectors` reader that is not a parameter here, which risks confusing the agent. The Args block is serviceable yet bloated by a 'ctx: MCP context' entry that adds nothing.

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 five-parameter mutation tool with no annotations and no output schema, the definition covers inputs adequately but omits return values, overwrite/error behavior, and permission requirements. It is roughly the minimum an agent needs to attempt a call, not a complete picture.

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

Parameters3/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 so partially by giving a one-line gloss for each of the five arguments, including the meaningful distinction between type_name ('Operator type name') and label ('Human-readable label'), plus the $JOB expansion note. However, the glosses are terse and leave format expectations (path syntax for node_path, valid version strings, name constraints) 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?

The first sentence gives a specific verb and resource: 'Create a new HDA from an existing subnet node,' which is far more than a restatement of the name. It does not explicitly name a contrasting sibling such as edit_hda_interface or install_hda, but the create-from-subnet framing is distinctive enough for an agent to place it.

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?

There is no when-to-use or when-not-to-use guidance and no reference to alternatives. An agent cannot tell from this text whether to reach for create_hda versus update_hda, install_hda, or set_hda_interface, or what prerequisites (existing subnet node, writable destination) must hold.

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