Skip to main content
Glama
dokaNc

IlluGen MCP

by dokaNc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Expose subgraph parameter

subgraph_expose_param
Idempotent

Expose an inner node parameter on a subgraph node so it can be adjusted from outside the subgraph.

Instructions

Shows a parameter of a node inside a subgraph on the subgraph node itself, so it can be tweaked from outside.

To build a subgraph: node_add('Subgraph'), then node_add and link_add with graph=<subgraph id> to add a
Node_Input (its label becomes an input pin name), the inner nodes and a Node_Output (its label becomes an
output pin name). Writes the project file in place.
Returns: id of the exposed parameter, node_id, param_name and label.

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).
labelNoName shown on the subgraph node. Empty = the parameter name.
paramYesParameter name on the inner node (see describe_node_type).
subgraphYesId or unique label of the Node_Subgraph node.
inner_nodeYesId or unique label of the node inside the subgraph.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.1.2
    • 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 / inner_node / description
      Added value: +"Id or unique label of the node inside the subgraph."
    • addedInput schema / properties / label / description
      Added value: +"Name shown on the subgraph node. Empty = the parameter name."
    • addedInput schema / properties / param / description
      Added value: +"Parameter name on the inner node (see describe_node_type)."
    • addedInput schema / properties / path / description
      Added value: +"Absolute path of the .illugen project file."
    • addedInput schema / properties / subgraph / description
      Added value: +"Id or unique label of the Node_Subgraph node."
  2. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations cover the safety profile (non-destructive, idempotent, writes), and the description usefully adds 'Writes the project file in place,' which tells the agent a side effect on disk occurs. It also states the return payload, which the absence of an output schema makes valuable.

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?

The purpose is front-loaded in the first sentence, followed by a compact workflow note and a returns line. The subgraph-construction aside is slightly tangential but short and contextually useful, with no filler.

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

Completeness4/5

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

With six parameters, a mutation side effect, and no output schema, the description covers the missing pieces: it states the file write and enumerates the returned fields. Only the relationship to invoking alternatives is left implicit.

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

Parameters3/5

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

Schema coverage is 100% and every parameter already carries a clear description, so the schema does the heavy lifting. The description adds no syntax or format detail beyond what the schema provides, so the baseline of 3 applies.

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 gives a specific verb+resource ('Shows a parameter of a node inside a subgraph on the subgraph node itself') and states the resulting behavior (expose for tweaking outside). It is clearly distinguishable from generic mutators like node_set, though it never names a sibling to contrast with.

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?

It supplies a prerequisite workflow (how to build a subgraph with node_add/link_add and Node_Input/Node_Output), which implies the context in which this tool is valid, but it never says when to prefer this over alternatives or when not to use 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