Skip to main content
Glama
ChengZiiii

opera-houdini-mcp

by ChengZiiii

reorder_inputs

Reorders input connections of a Houdini node by specifying a new input order list. Use it to rearrange or disconnect node inputs.

Instructions

重新排列节点的输入顺序。

参数说明:
- node_path: 目标节点路径。
- new_order: list of input_index,按新顺序排列(如 [2, 0, 1] 表示把
  原 input 2 移到 input 0,依此类推)。空 list 表示全部断开。
- order: 旧版别名;若同时传 new_order 与 order,以 new_order 为准。

返回 dict 包含 path / old_order / new_order / success 四项;
节点不存在时函数会抛 ValueError,bridge 不会再以 success:True 形式
静默吞错。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ctxYes
orderNo
new_orderNo
node_pathYes
Behavior4/5

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

With no annotations, the description discloses the return value format (dict with path/old_order/new_order/success) and the error behavior (throws ValueError on missing node, no silent swallowing). It also reveals the deprecated alias 'order' and the precedence rule. This adds non-obvious behavioral context beyond the operation name.

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?

The description is well-structured with a clear opening statement, bulleted parameter explanations, and a separate return/error note. It is concise yet thorough, with no filler or redundancy.

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?

The description covers return values and error behavior, and gives a concrete example. However, it leaves ambiguity about whether new_order must be a complete permutation of all input indices or can be a partial reorder, and it does not describe the 'ctx' parameter or constraints on index validity. Given the tool's moderate complexity, these are gaps that could lead to incorrect usage.

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

Parameters3/5

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

The description explains the semantics of node_path, new_order, and order in detail, including the mapping example and empty-list meaning, compensating for the 0% schema description coverage. However, it omits any explanation of the required 'ctx' parameter, and the schema types new_order/order as strings while the description calls them lists, creating ambiguity about the expected input format.

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?

The description clearly states the tool's function: '重新排列节点的输入顺序' (Reorder the input order of a node), which is a specific verb+resource. It further explains the semantics of new_order with an example ([2,0,1]), distinguishing it from generic connect/disconnect operations. This is a clear, non-tautological purpose.

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?

The description provides usage context by explaining the parameter meanings, including the empty-list behavior (disconnect all) and the precedence rule between new_order and order. However, it does not explicitly mention when to use this tool versus alternatives like connect_nodes or disconnect_node_input, nor does it state any prerequisites. So it's clear context but lacks exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ChengZiiii/opera-houdini-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server