Skip to main content
Glama
Sign In
healkeiser

fxhoudinimcp

by healkeiser
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_node_card

Get the authoritative documentation card for a node type, straight from the running Houdini: connectors in order (inputs / outputs with index, name and label — the index of texcoord on mtlximage lives here), real parameter…

Instructions

Get the authoritative documentation card for a node type, straight from the running Houdini: connectors in order (inputs / outputs with index, name and label — the index of texcoord on mtlximage lives here), real parameter names/defaults/menus, and the node's own shipped help text. Connectors are read off a probe node the first time a type is asked for in a session (no undo entry, creation scripts not run); connectors_probed: false with connectors_note means they could not be read, not that the type has none. A menu whose items a script computes (loadtype on filemerge::2.0) is read off the same probe and marked menu_source: "generator", with the script in menu_generator. A radio folder set (switcher1 on an Add SOP: By Pattern / By Group) is listed as a FolderSet parm whose menu is its folders; a default that is an expression ($F on timeshift's frame) is in default_expression; a VOP's outputs carry their data_type, and an output named after a parm's value carries named_by_parm (a Bind VOP's parm output is called whatever its parmname is). Parms the type's OnCreated script adds (Solaris edit-properties nodes: "Render Points As" on rendergeometrysettings is xn__primvarskarmaobjectpoint_style_zpbfg) are read off a second probe that runs it, listed with added_on_create and counted in parms_added_on_create. A VOP with several signatures lists them all in signatures (token, label, input types), and its signature menu is those tokens (menu_source: "signatures"), not only the one a fresh node's menu offers.

Use this BEFORE setting parameters on a node type you have not used in this session — never guess parameter names. Unversioned names resolve to the newest version.

A menu carries menu_labels (same order as menu) whenever its labels differ from its tokens: "0"/"1"/"2" = Surface Scatter/Keep Input/Volume Scatter.

Args: node_type: Type name (e.g. "scatter", "rbdbulletsolver"). context: Category — "Sop", "Lop", "Vop" (MaterialX and other shader nodes inside a material network), "Dop", "Cop", "Chop", "Top", "Object", "Driver"; also "Cop2", "Shop", "VopNet". parm_filter: Substring filter for the parameter list. include_help: The node's help text (about 4 KB). Default: included for a whole card, left out when parm_filter asks for specific parameters. Pass True or False to decide.

Input Schema

NameRequiredDescriptionDefault
contextNoSop
node_typeYes
parm_filterNo
include_helpNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.24.1
    • addedInput schema / additionalProperties
      Added value: +false
  2. Changed3 schema fields changedv2.21.0
    • addedInput schema / properties / include_help / anyOf
      Added value: +[
+  {
+    "type": "boolean"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / include_help / default
      Previous value: -trueNew value: +null
    • removedInput schema / properties / include_help / type
      Removed value: -"boolean"
  3. Changed1 schema field changedv2.18.0
    • addedInput schema / properties / include_help
      Added value: +{
+  "default": true,
+  "title": "Include Help",
+  "type": "boolean"
+}
  4. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

No annotations are provided, so the description carries the full burden and does so richly: it discloses that connectors are read off a probe node on first ask (no undo entry, creation scripts not run), that a second probe runs the OnCreated script, and that connectors_probed:false means 'could not be read, not that the type has none.' It also documents menu_source, added_on_create, named_by_parm, and signature semantics — substantial side-effect and interpretation disclosure.

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 usage before the dense field-level detail, and each clause conveys real semantics (edge cases for menus, folders, expressions, VOP signatures). It is very long and heavy with parenthetical examples, but because there is no output schema the return-field explanation earns much of its length.

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 annotations, no output schema, and 0% schema coverage across 4 parameters, the description still covers purpose, when-to-use, side effects, argument meaning, and the semantics of returned fields (menu_labels, data_type, signatures, connectors_probed). An agent has everything needed to select and invoke it correctly.

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 description coverage is 0%, so the description must compensate, and it does: it documents node_type with examples, enumerates all valid context values (Sop/Lop/Vop/Dop/Cop/Chop/Top/Object/Driver plus Cop2/Shop/VopNet), explains parm_filter as a substring filter, and clarifies include_help's conditional default behavior. Only minor gap is that no type/format constraints are spelled out beyond examples.

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 with scope: 'Get the authoritative documentation card for a node type, straight from the running Houdini,' and immediately enumerates what the card contains (connectors, parameter names/defaults/menus, help text). This clearly distinguishes it from siblings like get_parameter_schema, get_parameters, and list_node_types.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit when-to-use: 'Use this BEFORE setting parameters on a node type you have not used in this session — never guess parameter names,' plus a versioning rule ('Unversioned names resolve to the newest version'). It gives clear context but does not explicitly name alternative tools (e.g., get_parameter_schema) or state exclusions.

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