Skip to main content
Glama

link_parameters

Create a relative HScript channel reference from a source parameter to a destination parameter, preserving links when nodes move and refusing to overwrite existing animation unless allowed.

Instructions

Create a channel reference from one parameter to another.

The destination gets an HScript expression that reads the source as its own type: chs() for a String parameter, ch() for numbers, toggles and menus. The path is relative to the destination node (chs("../CTRL/mat")), so the link survives moving the pair, collapsing into a subnet or instancing an HDA. The reply carries the expression, the function used and the destination's evaluated value.

Two ramps (or two multiparms) are linked entry by entry as well, now and whenever the source gains or loses keys: the opmultiparm links Promote Parameter makes. The reply lists multiparm_links and follows_source. Inside an asset, update_hda afterwards to keep the link in its contents.

Args: source_path: Source node path. source_parm: Source parameter name. dest_path: Destination node path. dest_parm: Destination parameter name. replace_existing: Overwrite a destination that already has keyframes or an expression. Refused otherwise, so animation is never lost by accident. A link whose source already reads the destination through ch() is refused as a cycle in every case.

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. Changed1 schema field changedv2.24.1
    • addedInput schema / additionalProperties
      Added value: +false
  2. Changed1 schema field changedv2.19.0
    • addedInput schema / properties / replace_existing
      Added value: +{
      +  "default": false,
      +  "title": "Replace Existing",
      +  "type": "boolean"
      +}
  3. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so well: it discloses the side effect (an expression is installed on the destination), the relative-path semantics that make the link survive moves/subnets/HDAs, the refusal conditions (existing keyframes or expression without replace_existing; cycles always refused), and the multiparm entry-by-entry linking behavior that continues as keys change.

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?

Front-loaded with the one-line purpose, then mechanism, then edge cases, then arguments — a sensible progression. Every paragraph carries information, though the Args block partially restates the schema property titles and could be tightened.

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

Completeness5/5

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

For a five-parameter mutation tool with no annotations and no output schema, the description covers what an agent needs: side effects, path format, refusal/cycle rules, the follow-up update_hda step, and even the shape of the reply (expression, function used, evaluated value, multiparm_links, follows_source).

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

Parameters4/5

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

Schema coverage is 0%, so the Args block is doing real work. The four path/parm arguments get only terse glosses ("Source node path"), but the important semantic — the path being relative to the destination node, with the "../CTRL/mat" example — is stated in the body, and replace_existing is explained in depth including its default-false refusal consequence.

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?

States a precise verb and resource ("Create a channel reference from one parameter to another") and immediately explains the mechanism: an HScript expression (chs()/ch()) written into the destination. That mechanism makes it unmistakably distinct from value-writing siblings like set_parameters or get_parameters without needing to name them.

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?

Gives concrete conditional guidance: replace_existing must be set to overwrite a destination with keyframes or an expression, and the link is refused when a cycle would form. It also routes the agent onward ("Inside an asset, update_hda afterwards"). It stops short of explicitly contrasting with set_parameters/connect_nodes-style alternatives, so no full when-not/alternative mapping.

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