Skip to main content
Glama
Sign In
Houdini MCP

Houdini MCP

by beatreichenbach
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

set_wrangle_code

Set VEX code on an existing Attribute Wrangle node to update its behavior without recreating the node.

Instructions

Set VEX code on an existing 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>",
      "vex_code": "<vex_code>"
    },
    "name": "set_wrangle_code"
  }
}

Input Schema

NameRequiredDescriptionDefault
vex_codeYes
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 provided, so the description must carry the full behavioral burden. It implies a mutation that overwrites VEX code on an existing node, but does not state permissions, whether existing code is replaced entirely, error behavior for invalid node paths, or whether the node must already exist beyond the vague 'existing' qualifier.

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?

A single front-loaded sentence with no wasted words. The action, target, and constraint ('existing') are stated immediately.

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

Completeness2/5

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

For a mutation tool with two required parameters, no annotations, no output schema, and 0% schema description coverage, the description is thin. It omits what the operation returns, error conditions, and how the node is identified, leaving key invocation details unaddressed.

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?

Schema description coverage is 0%, and the schema titles ('Vex Code', 'Node Path') already convey the parameter names. The description adds only that node_path refers to an 'existing Attribute Wrangle node'; it gives no format examples, path syntax, or VEX code expectations.

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 names a specific verb ('Set'), resource ('VEX code'), and target ('existing Attribute Wrangle node'). The word 'existing' subtly distinguishes it from create_wrangle, but no sibling is explicitly named, keeping it 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 explicit when-to-use guidance or mention of alternatives. The word 'existing' implies you should already have a node, but the description never says to use create_wrangle when no node exists or get_wrangle_code to read code first.

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