Skip to main content
Glama
healkeiser

fxhoudinimcp

by healkeiser
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_node_card

Retrieve documentation for a Houdini node type from running Houdini, including parameter names, defaults, connectors, and help text. Use before setting parameters to avoid guessing.

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.

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

TableJSON 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.7/5.0
Behavior5/5

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

No annotations, so the description carries full burden — and it does so exceptionally well: it discloses the side effect that connectors are read off a probe node (no undo entry, creation scripts not run), the meaning of `connectors_probed: false` vs. genuinely having no connectors, and how generated menus / folder sets / expression defaults are surfaced. This is exactly the behavioral context an agent needs before invoking.

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?

Long, but front-loaded with purpose and the use-before rule, and the dense edge-case sentences (menu_source generator, FolderSet, default_expression, data_type) substitute for the absent output schema. A few clauses are niche, 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.

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 description coverage, the description almost fully carries the load: it explains return structure (connectors, menus, defaults, help), the probing side effect, and default behaviors of optional params. 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, and it does: node_type with examples, context with the full enumerated category list (Sop/Lop/Vop/Dop/Cop/Chop/Top/Object/Driver plus Cop2/Shop/VopNet), parm_filter as a substring filter, and include_help with its default-inclusion rule. All four parameters are given meaning beyond their bare names.

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 precise verb+resource ('Get the authoritative documentation card for a node type') and immediately scopes it as coming 'straight from the running Houdini', which distinguishes it from static help tools like search_help or get_parameter_schema. An agent can tell what it returns (connectors, parm names/defaults/menus, help text) without opening the schema.

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?

Gives an explicit when-to-use rule ('BEFORE setting parameters on a node type you have not used in this session — never guess parameter names') and notes that unversioned names resolve to newest. Strong context, though it does not name a specific alternative sibling (e.g. get_parameter_schema) for the case when the type IS known.

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