Skip to main content
Glama
Sign In
Houdini MCP

Houdini MCP

by beatreichenbach
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

build_sop_chain

Creates a sequential chain of SOP nodes wired together in a single call, reducing manual node setup in Houdini workflows.

Instructions

Build a sequential chain of SOP nodes wired together in a single call.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "build_sop_chain"
  }
}

Input Schema

NameRequiredDescriptionDefault
stepsNo
parent_pathNo/obj/geo1

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?

No annotations are supplied, so the description carries the full burden. It does not say whether nodes are newly created or existing nodes are referenced, what happens to the parent_path container, whether existing chains are mutated, how failures/partial chains are handled, or what is returned.

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. It is efficient, though the terseness contributes to the specification gaps rather than offsetting them.

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

Completeness1/5

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

For a tool that constructs a whole node chain from arbitrary step objects, with no annotations, no output schema, and zero parameter documentation, one sentence is far too little. An agent cannot construct a valid call from this definition alone.

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 two undocumented parameters. The description hints that the steps items are SOP nodes, but gives no clue about the shape of each step object (node type, parameters, wiring) or the role and default of parent_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?

"Build a sequential chain of SOP nodes wired together in a single call" names a specific verb and resource and conveys the batching idea. It does not, however, contrast itself with obvious siblings such as connect_nodes_batch or create_node, so the agent must infer the boundary.

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, no prerequisites, and no named alternative. "In a single call" faintly implies it replaces repeated connect calls, but no condition selecting this tool over siblings is 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