Skip to main content
Glama
Sign In
Houdini MCP

Houdini MCP

by beatreichenbach
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

change_node_type

Change a node's type in place, preserving wires, parameters, and network contents when updating Houdini workflows.

Instructions

Change a node's type in place, preserving wires and parameters.

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>",
      "new_type": "<new_type>"
    },
    "name": "change_node_type"
  }
}

Input Schema

NameRequiredDescriptionDefault
new_typeYes
keep_nameNo
node_pathYes
keep_parmsNo
keep_network_contentsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose the important preservation semantics (wires and parameters survive), but omits what happens to parameters that are invalid for the new type, whether the change is reversible, and what errors look like. The schema's keep_name/defaults suggest conditional preservation that the description never explains.

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?

A single front-loaded sentence with no filler; every clause contributes. It is efficient, though brevity comes at the cost of detail covered in other dimensions.

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 five-parameter mutation tool with no annotations, no output schema, and zero schema descriptions, one sentence is not enough. An agent still lacks valid type values, findability of node_path, and the semantics of the three keep_* flags.

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% with five parameters. "Preserving wires and parameters" loosely maps to keep_network_contents and keep_parms, but keep_name and node_path are never addressed, and no valid values for new_type are given. The description partially compensates but leaves most parameter meaning undocumented.

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?

States a specific verb and resource ("Change a node's type") with the key qualifier "in place," so an agent can distinguish it from create_node/delete_node/rename_node. It stops short of explicitly naming an alternative, but the operation itself is unambiguous.

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

Usage Guidelines3/5

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

Usage is only implied: "in place, preserving wires and parameters" hints that this is the right choice when you want to retype a node without rebuilding its connections. There is no explicit when-to-use vs. delete-and-recreate guidance, and no prerequisites (node must exist, valid type names) are stated.

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