Skip to main content
Glama
dokaNc

IlluGen MCP

by dokaNc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Get node

node_get
Read-onlyIdempotent

Retrieve full details of a node—parameters, curves, gradients, spline points, pins, and links—before editing. Read-only; use to inspect exact names and current values.

Instructions

Returns every detail of one node: parameter values, curves, gradients, spline points, pins and links.

Use it before node_set, curve_set, gradient_set, spline_set or node_set_data to see current values and exact
names; use project_summary for the whole graph. Offline and read-only.
Returns: id, type, label, pos, disabled, params {name: value} ('<driven by link>' when a Signal drives it),
curves {name: [[position, value], ...]}, gradients, spline_points, subgraph pins for subgraphs,
parameter_pins, outgoing and incoming links, known_inputs and known_outputs.

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).
node_idYesNode id as a string (from project_summary or node_add), or the node's label if it is unique.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 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 / node_id / description
      Added value: +"Node id as a string (from project_summary or node_add), or the node's label if it is unique."
    • addedInput schema / properties / path / description
      Added value: +"Absolute path of the .illugen project file."
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world); the description still adds the 'Offline' trait and a detailed return contract, including the '<driven by link>' sentinel for Signal-driven params, which annotations cannot express. It stops short of noting pagination or size limits, but for a single-node read that is minor.

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?

Purpose and usage routing come first, followed by the return enumeration; every clause carries information. The Returns block is long but justified because no output schema exists, so the size is earned rather than padding.

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 no output schema, the description takes on the full burden of describing the response and does so field by field, including nested params, curves, gradients, pins and links. Combined with the pre-setter usage rule, an agent has everything needed to call and interpret this tool.

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 description coverage is 100%, so path, graph and node_id are already fully documented, and the description adds nothing about their syntax. It reinforces the node_id source (project_summary/node_add) that the schema also states, which is baseline-appropriate but not additive.

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 specific verb (get) and resource (one node) plus the exact payload scope (parameters, curves, gradients, spline points, pins, links). It also names the setters it complements and the sibling (project_summary) that covers the rest of the graph, so an agent can place it instantly.

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

Usage Guidelines5/5

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

Explicitly says to call it before node_set, curve_set, gradient_set, spline_set and node_set_data to learn current values and exact names, and points to project_summary for whole-graph inspection. Both the when and the alternative are spelled out.

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