Skip to main content
Glama
Sign In
Houdini MCP

Houdini MCP

by beatreichenbach
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

link_parameters

Creates a channel reference from one Houdini parameter to another, connecting source and destination parameters and optionally replacing existing links.

Instructions

Create a channel reference from one parameter to another.

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": {
      "source_path": "<source_path>",
      "source_parm": "<source_parm>",
      "dest_path": "<dest_path>",
      "dest_parm": "<dest_parm>"
    },
    "name": "link_parameters"
  }
}

Input Schema

NameRequiredDescriptionDefault
dest_parmYes
dest_pathYes
source_parmYes
source_pathYes
replace_existingNo

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 behavioral burden. It implies a mutation (references are created) but says nothing about permission requirements, what happens if a reference already exists, whether replacing an existing link is destructive, or what the result looks like. One sentence is insufficient for a state-changing tool with zero annotation coverage.

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?

A single sentence with no wasted words, but it is under-specified rather than concise. There is no structure to front-load the key operational facts an agent needs, such as path/parm pairing or overwrite behavior.

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?

With five parameters, four required, no annotations, and no output schema, the definition needs more disclosure than one sentence. The agent lacks guidance on argument semantics and side effects, leaving it unable to call this tool confidently without opening the schema and guessing.

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 the description must compensate and does not. It implies a source and destination but never explains the distinction between *_path and *_parm arguments, nor the meaning of replace_existing, which is the one parameter whose semantics materially change behavior (overwrite vs. fail).

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 concrete verb and resource: 'Create a channel reference from one parameter to another.' An agent can tell this is about parameter linking, though it does not distinguish itself from siblings like connect_nodes or set_parameters. The term 'channel reference' is domain jargon that isn't defined.

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?

The description gives no when-to-use guidance, no prerequisites, and no mention of alternatives such as set_parameters or connect_nodes. The agent must infer that this is the tool for wiring one parameter's value to another, without any stated conditions or exclusions.

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