Skip to main content
Glama
Sign In
Houdini MCP

Houdini MCP

by beatreichenbach
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

set_node_position

Sets a Houdini node's X/Y position in the network editor using its node path, so you can organize or align nodes programmatically.

Instructions

Set a node's position in the network editor.

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>",
      "x": "<x>",
      "y": "<y>"
    },
    "name": "set_node_position"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYes
yYes
node_pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries the full burden but discloses nothing beyond the basic action. It does not say whether the operation is undoable, whether it requires the node to exist in the current network, whether it triggers a cook/re-render, or what happens if coordinates are outside the visible editor area.

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 short sentence that front-loads the action and resource with no filler. It is terse rather than padded, though the terseness is the source of the missing detail rather than a virtue here.

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 three-parameter required-argument mutation tool with no annotations, no output schema, and 0% schema description coverage, this one-liner is not enough. An agent could guess at x/y but would still be uncertain about node_path format and coordinate semantics.

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%, so x, y, and node_path are documented only by bare titles. The description does not clarify the coordinate system or units, whether coordinates are absolute or relative, or the expected format of node_path.

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') and resource ('a node's position'), plus the context ('in the network editor'), so the operation is intelligible on its own. It does not distinguish itself from sibling tools like move_node, leaving potential overlap for the agent to guess at.

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 guidance on when to use this versus move_node or other positioning-related tools, and no mention of prerequisites such as whether the target node's network must be the current network. The agent must infer all of this.

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