Skip to main content
Glama
healkeiser

fxhoudinimcp

by healkeiser
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_parm_template_tree

Get the full parameter interface as a tree for a Houdini node or type, including folders, defaults, ranges, menus, and conditionals, to understand the structure before editing.

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
folderNo
contextNoSop
node_pathNo
type_nameNo
max_entriesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.18.0

TDQS

A5/5.0
Behavior5/5

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

With no annotations provided, the description carries full behavioral disclosure. It explains what the returned tree contains, that node_path includes spares, that entries use get_parameter_schema's keys, and that max_entries caps results with an indication in the reply when truncation occurs. The phrase 'read this before editing' also implies a non-mutating, read-only operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is detailed but every sentence earns its place: high-level definition, differentiation from siblings, usage guidance, and a compact Args block. It is front-loaded with the most important distinguishing information before moving into parameters.

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 parameter-introspection tool with no annotations and no output schema, this description is unusually complete. It explains the return shape, the selection modes, the folder-filtering mechanism, the truncation behavior, and the relationship to sibling schemas, so an agent has enough to call it correctly.

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%, but the description compensates by documenting all five parameters: node_path, type_name, context, folder, and max_entries. It adds real meaning beyond the schema by explaining folder's nested-label behavior and max_entries' depth-first cap and cut notification.

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 description states the tool's resource precisely: the full parameter interface represented as a tree, with folders, parameter order, defaults, expressions, ranges, menu items, and conditionals. It also explicitly distinguishes itself from get_hda_info and get_parameter_schema, making it easy for an agent to select this tool over nearby siblings.

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?

The description gives concrete usage context: it should be read before editing an interface, and it explains why get_hda_info and get_parameter_schema are insufficient for that purpose. It also tells the agent how to address the target via node_path or type_name + context, covering the main selection paths.

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