Skip to main content
Glama
Sign In
Houdini MCP

Houdini MCP

by beatreichenbach
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_wrangle_code

Reads VEX code from a Houdini Attribute Wrangle node using its node path, so you can inspect and reuse the node's current code.

Instructions

Read the VEX code from an Attribute Wrangle node.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "node_path": "<node_path>"
    },
    "name": "get_wrangle_code"
  }
}

Input Schema

NameRequiredDescriptionDefault
node_pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and discloses almost nothing. It implies a read-only operation but says nothing about permissions, what happens when node_path points to a non-wrangle or missing node, whether the code is returned as raw text, or how errors surface.

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?

One short sentence, front-loaded with the verb and resource, with no filler. It is efficient but borders on under-specification given the total absence of parameter and behavior detail.

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

Completeness3/5

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

For a low-complexity single-parameter read tool with no output schema, the description states enough to identify the operation. However, it leaves the only parameter's format and the failure modes undocumented, which is more than a minimal gap for a tool an agent must call with a correct Houdini node path.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single required parameter, node_path, has 0% schema description coverage, and the description does not compensate. It never states the expected path syntax, whether it is an absolute Houdini node path like /obj/geo1/attribwrangle1, or how it relates to the Attribute Wrangle restriction.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ("Read") and a specific resource ("the VEX code from an Attribute Wrangle node"), which is more precise than the name alone and implicitly separates it from the mutating sibling set_wrangle_code. It stops short of naming or contrasting that sibling explicitly, so it lands at 4 rather than 5.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no stated prerequisites (e.g. the node must exist and be an Attribute Wrangle), and no mention of set_wrangle_code as the counterpart for writing code. The usage is only inferable from the verb "Read".

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