Skip to main content
Glama
dokaNc

IlluGen MCP

by dokaNc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Link pins

link_add
Idempotent

Connect an output pin to an input pin in an IlluGen node graph, replacing existing links and rejecting pin type mismatches. Writes the project file.

Instructions

Connects an output pin of one node to an input pin of another.

Any existing connection into that input is replaced. Pin data kinds are checked (Grayscale, Color, UV...) and
a mismatch fails with an explanation. Parameter pins (e.g. 'Scale', 'Seed') let a Signal node (Oscillator,
Cycle, Constant...) drive a parameter; optional inputs (e.g. Levels 'In Low mod') are exposed automatically.
Subgraph pins are the labels of the subgraph's inner Node_Input/Node_Output nodes. Writes the project file in
place.
Returns: link {from_node, from_pin, to_node, to_pin} and warnings if any.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesAbsolute path of the .illugen project file.
graphNoGraph to work in: empty for the top-level graph, or the id or label of a Node_Subgraph node ('outer/inner' for nested subgraphs).
to_pinYesInput pin name on the destination node: a regular input, a parameter pin or a subgraph input.
to_nodeYesDestination node id or unique label.
from_pinYesOutput pin name on the source node (see describe_node_type).
from_nodeYesSource node id or unique label.
modulation_rangeNoOnly for parameter pins: [min, max] in 0..1 of the parameter range the Signal sweeps, or one [min, max] pair per vector component. Default: the full range.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv0.1.2
    • addedInput schema / properties / from_node / description
      Added value: +"Source node id or unique label."
    • addedInput schema / properties / from_pin / description
      Added value: +"Output pin name on the source node (see describe_node_type)."
    • addedInput schema / properties / graph / description
      Added value: +"Graph to work in: empty for the top-level graph, or the id or label of a Node_Subgraph node ('outer/inner' for nested subgraphs)."
    • addedInput schema / properties / modulation_range / description
      Added value: +"Only for parameter pins: [min, max] in 0..1 of the parameter range the Signal sweeps, or one [min, max] pair per vector component. Default: the full range."
    • addedInput schema / properties / path / description
      Added value: +"Absolute path of the .illugen project file."
    • addedInput schema / properties / to_node / description
      Added value: +"Destination node id or unique label."
    • addedInput schema / properties / to_pin / description
      Added value: +"Input pin name on the destination node: a regular input, a parameter pin or a subgraph input."
  2. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Goes well past annotations: discloses that an existing input connection is replaced, that pin data kinds are validated with an explanatory failure, and that the project file is written in place. The write-in-place note is the meaningful complement to readOnlyHint=false. There is mild tension with destructiveHint=false given the silent replacement of an existing connection, but replacing a link is recoverable and not a hard contradiction.

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-loads the core operation in one sentence, then layers edge-case semantics. Dense but every sentence carries information (validation, replacement, parameter/subgraph pins, side effect, return value). Slightly long across four paragraphs but no filler.

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?

With 7 parameters, no output schema, and a mutation that alters an existing graph, this description covers the essentials: replacement semantics, validation failure mode, pin-kind categories, side effect on disk, and the return shape (link object plus warnings). Nothing critical for a correct call is missing.

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 100%, so the baseline is 3, but the description adds real meaning: parameter pins let a Signal node drive a parameter, optional inputs are exposed automatically, and subgraph pins map to inner Node_Input/Node_Output labels. It does not elaborate on modulation_range syntax beyond what the schema already states.

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?

Opens with a precise verb+resource: 'Connects an output pin of one node to an input pin of another.' This cleanly separates it from sibling link_remove and from node-level tools like node_set. No ambiguity about what operation is performed.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage context is implied but never stated as when-to-use. It never names link_remove or explains when to re-link vs. modify an existing node, and gives no prerequisites (e.g. node must already exist). The description does explain the input-replacement semantics, which is the closest thing to guidance.

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