Skip to main content
Glama
healkeiser

fxhoudinimcp

by healkeiser
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_parm_template_tree

Read a Houdini node or asset type's complete parameter interface as an ordered tree—folders, parameters, defaults, menus, hide/disable rules, and callback metadata.

Instructions

The whole parameter interface as a tree, the way Type Properties shows it: folders (with folder_type — tabs, collapsible, multiparm), every parameter in order with defaults, default expressions, ranges, menu items, Hide/Disable When conditionals, callbacks, naming scheme; a multiparm's default_instances. Each entry uses get_parameter_schema's keys (default_value, is_hidden, menu_items...).

get_hda_info shows only the top folders and get_parameter_schema flattens the structure away; read this before editing an interface. Give node_path for a node (its instance interface, spares included) or type_name + context for a type.

Args: node_path: Node whose interface to read. type_name: Node type instead (with context). context: Category of type_name — "Sop", "Object", "Lop", ... folder: Narrow to one folder by label, or a list of nested labels. max_entries: Cap on entries (depth-first); the reply says when it cut. include_tags: Also return each template's tags (needed to preserve them when editing an interface; about a quarter of the size).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
folderNo
contextNoSop
node_pathNo
type_nameNo
max_entriesNo
include_tagsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.24.1
    • addedInput schema / additionalProperties
      Added value: +false
  2. Changed2 schema fields changedv2.21.0
    • addedInput schema / properties / include_tags
      Added value: +{
+  "default": false,
+  "title": "Include Tags",
+  "type": "boolean"
+}
    • changedInput schema / properties / max_entries / default
      Previous value: -400New value: +150
  3. Addedv2.18.0

TDQS

A4.7/5.0
Behavior4/5

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

No annotations exist, so the description carries the full behavioral burden, and it does substantial work: it enumerates what the tree contains (folders with folder_type values, defaults, expressions, ranges, menu items, conditionals, callbacks, default_instances), discloses truncation behavior for max_entries ('the reply says when it cut'), and quantifies the cost of include_tags ('about a quarter of the size'). It never explicitly states that the call is side-effect-free, but the read-only nature is unambiguous from the content.

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 the return payload, then the sibling differentiation, then an Args block — a sensible order. The first paragraph is a long enumeration but each item is load-bearing; only minor density cost keeps this from a 5.

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?

With no output schema and no annotations, the description is the sole source of truth, and it covers return shape (keys match get_parameter_schema's, e.g. default_value, is_hidden, menu_items), nesting semantics, truncation, and all six inputs. Nothing an agent needs to call it correctly 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 fully, and it does: every one of the six args is explained, including the folder union type ('one folder by label, or a list of nested labels'), context with concrete enum-like examples ('Sop', 'Object', 'Lop'), max_entries as a depth-first cap with truncation notice, and the preservation rationale for include_tags.

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 — returning the whole parameter interface as a tree — and immediately names the two siblings it differs from (get_hda_info, get_parameter_schema), explaining exactly how each falls short. An agent can distinguish this from every other introspection tool 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?

Explicit routing: 'read this before editing an interface', with the alternatives and their limitations spelled out ('get_hda_info shows only the top folders', 'get_parameter_schema flattens the structure away'). Also states the node_path vs type_name+context selection rule, so the caller knows which branch to take.

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