Skip to main content
Glama
Sign In
Houdini MCP

Houdini MCP

by beatreichenbach
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

connect_nodes_batch

Connect multiple node pairs in one call to set up several Houdini node connections at once, reducing repetitive wiring steps.

Instructions

Connect multiple node pairs in a single call.

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": {
      "connections": "<connections>"
    },
    "name": "connect_nodes_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
connectionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/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 behavioral burden and does not meet it. It says nothing about whether the batch is atomic, what happens if some pairs fail, whether nodes must already exist, or what the caller gets back.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One front-loaded sentence with no filler, which is structurally clean, but it is terse to the point of under-specification for a batch mutation. Brevity here costs information rather than saving it.

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?

A batch write tool with zero annotation coverage, no output schema, and an entirely undocumented parameter structure needs considerably more explanation. Key facts an agent needs — item shape, failure semantics, return value — are all absent.

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 coverage is 0% and the single connections parameter is an array of untyped objects with additionalProperties true. The description hints each element is a "node pair" but never gives the item field names (e.g. source/target) or ordering rules, so the agent cannot construct valid input from the definition alone.

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 ("Connect") and resource ("node pairs") and adds the batch scope ("multiple ... in a single call"), which distinguishes it from the singular connect_nodes sibling. It stops short of naming that sibling explicitly, but the operation 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 Guidelines2/5

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

There is no stated when-to-use or when-not-to-use guidance. The phrase "in a single call" implies a batching use case versus connect_nodes, but the agent is left to infer that trade-off rather than being told it.

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