HoudiniMCP

Overview Schema Source Related Servers Discussions Admin

hda

Destructive

Read, create, install, reload, and edit Houdini digital assets: inspect definitions and sections, load asset files, save subnet changes, and manage asset scripts or help.

Instructions

Read and change Houdini digital assets.

Use it when a node type comes from a .hda file: to find the file, to load a
new one, or to read the scripts and the help inside it.

Do not use it for the parameters of one node in the scene: node_inspect
does that.

mode:
    "list"        — the installed assets. `category` filters, for example
                    "Sop".
    "get"         — the definition of `node_type`: the file, the version
                    and the tools.
    "install"     — load the .hda file at `file_path` into the session.
    "uninstall"   — unload the .hda file at `file_path`.
    "reload"      — read the .hda file at `file_path` again, after an edit
                    on disk.
    "update"      — save the node at `node_path` back into its asset.
    "create"      — make an asset from the subnet at `node_path`, with
                    `name`, `label` and `file_path`.
    "sections"    — the section names inside `node_type`.
    "section_get" — the text of `section_name`, for example "PythonModule".
    "section_set" — write `content` into `section_name`.

Returns JSON. "install" and "uninstall" change every node of that type in
the session.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`mode`	No	One of "list", "get", "install", "uninstall", "reload", "update", "create", "sections", "section_get", "section_set".	list
`name`	No	create: the type name of the new asset.
`label`	No	create: the name that the TAB menu shows.
`content`	No	section_set: the text to write into the section.
`category`	No	list: keep one node category, for example "Sop".
`file_path`	No	install, uninstall, reload: the .hda file. create: the file to write.
`node_path`	No	update: the node to save into its asset. create: the subnet to make an asset from.
`node_type`	No	get, sections, section_get, section_set: the asset type, as list names it, for example "labs::edge_damage::1.0", or with its category, "Sop/labs::edge_damage::1.0".
`section_name`	No	section_get, section_set: the section, for example "PythonModule".

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.7.5Oct 4, 2026

changedInput schema / properties / node_type / description

Previous value: -"get, sections, section_get, section_set: the asset type, for example \"Sop/my_tool\"."New value: +"get, sections, section_get, section_set: the asset type, as list names it, for example \"labs::edge_damage::1.0\", or with its category, \"Sop/labs::edge_damage::1.0\"."

Changed45 schema fields changedv0.7.3Oct 4, 2026
- removedInput schema / properties / category / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / category / default
```
Removed value: -null
```
- addedInput schema / properties / category / description
```
Added value: +"list: keep one node category, for example \"Sop\"."
```
- removedInput schema / properties / category / title
```
Removed value: -"Category"
```
- addedInput schema / properties / category / type
```
Added value: +"string"
```
- removedInput schema / properties / content / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / content / default
```
Removed value: -null
```
- addedInput schema / properties / content / description
```
Added value: +"section_set: the text to write into the section."
```
- removedInput schema / properties / content / title
```
Removed value: -"Content"
```
- addedInput schema / properties / content / type
```
Added value: +"string"
```
- removedInput schema / properties / file_path / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / file_path / default
```
Removed value: -null
```
- addedInput schema / properties / file_path / description
```
Added value: +"install, uninstall, reload: the .hda file. create: the file to write."
```
- removedInput schema / properties / file_path / title
```
Removed value: -"File Path"
```
- addedInput schema / properties / file_path / type
```
Added value: +"string"
```
- removedInput schema / properties / label / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / label / default
```
Removed value: -null
```
- addedInput schema / properties / label / description
```
Added value: +"create: the name that the TAB menu shows."
```
- removedInput schema / properties / label / title
```
Removed value: -"Label"
```
- addedInput schema / properties / label / type
```
Added value: +"string"
```
- removedInput schema / properties / mode / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedInput schema / properties / mode / description
```
Added value: +"One of \"list\", \"get\", \"install\", \"uninstall\", \"reload\", \"update\", \"create\", \"sections\", \"section_get\", \"section_set\"."
```
- removedInput schema / properties / mode / title
```
Removed value: -"Mode"
```
- addedInput schema / properties / mode / type
```
Added value: +"string"
```
- removedInput schema / properties / name / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / name / default
```
Removed value: -null
```
- addedInput schema / properties / name / description
```
Added value: +"create: the type name of the new asset."
```
- removedInput schema / properties / name / title
```
Removed value: -"Name"
```
- addedInput schema / properties / name / type
```
Added value: +"string"
```
- removedInput schema / properties / node_path / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / node_path / default
```
Removed value: -null
```
- addedInput schema / properties / node_path / description
```
Added value: +"update: the node to save into its asset. create: the subnet to make an asset from."
```
- removedInput schema / properties / node_path / title
```
Removed value: -"Node Path"
```
- addedInput schema / properties / node_path / type
```
Added value: +"string"
```
- removedInput schema / properties / node_type / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / node_type / default
```
Removed value: -null
```
- addedInput schema / properties / node_type / description
```
Added value: +"get, sections, section_get, section_set: the asset type, for example \"Sop/my_tool\"."
```
- removedInput schema / properties / node_type / title
```
Removed value: -"Node Type"
```
- addedInput schema / properties / node_type / type
```
Added value: +"string"
```
- removedInput schema / properties / section_name / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / section_name / default
```
Removed value: -null
```
- addedInput schema / properties / section_name / description
```
Added value: +"section_get, section_set: the section, for example \"PythonModule\"."
```
- removedInput schema / properties / section_name / title
```
Removed value: -"Section Name"
```
- addedInput schema / properties / section_name / type
```
Added value: +"string"
```
- removedInput schema / title
```
Removed value: -"toolArguments"
```
Addedv0.1.1Oct 4, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false; the description adds the key scope warning that 'install' and 'uninstall' change every node of that type in the session, and notes the return type (JSON). It does not call out which modes are read-only vs mutating explicitly, but the destructive blast radius is disclosed.

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 routing, then a well-structured mode-by-mode list where each line adds actionable detail. Slightly verbose overall but nearly every sentence earns its place.

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

Completeness4/5

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

An output schema exists so return values needn't be explained, and the description covers all ten modes with their parameter bindings plus the session-wide side effect. Complete enough for correct invocation, with only minor gaps in per-mode read/write labeling.

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 100%, so the schema already binds each parameter to its modes (the baseline would be 3). The description adds semantic value by explaining what each mode does with the parameters, e.g. section_set writes `content` into `section_name` and install loads the file at `file_path`.

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+resource ('Read and change Houdini digital assets') and immediately scopes the domain to .hda files. It explicitly distinguishes itself from the sibling node_inspect, so an agent can route correctly without opening schemas.

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?

Gives explicit when-to-use ('when a node type comes from a .hda file') and when-not ('Do not use it for the parameters of one node in the scene: node_inspect does that'), naming the alternative. The mode list further maps each intent to an action.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

hda

Instructions

Input Schema

Output Schema

Schema Changelog

TDQS

Other Tools