Skip to main content
Glama
dokaNc

IlluGen MCP

by dokaNc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Describe node type

describe_node_type
Read-onlyIdempotent

Retrieve a node type's parameters, curves, and typed input/output pins before adding or linking it, so you use valid names, kinds, defaults, and pin data kinds.

Instructions

Describes one node type: its parameters, curves and typed input/output pins.

Call it before node_add or node_set to get valid parameter names, value kinds, defaults, enum values and UI
ranges, and before link_add to get pin names and the data kind each pin carries. Offline and read-only.
Pin kinds: Grayscale, Color, UV, Normal, Islands, GeometryBuffer...; 'Inherit' takes the kind of whatever is
connected; 'Signal' is a modulator (Oscillator, Cycle, Constant...).
Returns: type, category, params {name: {kind, default, values for enums, min/max, label, modulatable}},
curves, pins {inputs, outputs, optional_inputs} and parameter_pins {pin name: parameter it drives when a
Signal is linked to it, e.g. 'Scale', 'Seed'}. An unknown type fails with close-match suggestions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
node_typeYesNode type name from list_node_types. Case, spaces and the 'Node_' prefix are optional, e.g. 'grayscale noise' for Node_Grayscale_Noise.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.2
    • addedInput schema / properties / node_type / description
      Added value: +"Node type name from list_node_types. Case, spaces and the 'Node_' prefix are optional, e.g. 'grayscale noise' for Node_Grayscale_Noise."
  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 declare read-only/idempotent/non-destructive, and the description reinforces with 'Offline and read-only', then goes further by disclosing return shape, the pin-kind taxonomy (Grayscale, Color, Signal, Inherit), and error behavior ('unknown type fails with close-match suggestions'). That failure-mode and return-content detail is genuine added value beyond the annotations.

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 when-to-use are front-loaded in the first two sentences, with return details grouped after. It is on the longer side and the pin-kind enumeration is dense, but every sentence carries usable context and nothing is redundant with the schema.

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 steps in to describe the return payload in detail (params structure, curves, inputs/outputs/optional_inputs, parameter_pins mapping) as well as the error path, so an agent has everything needed to call and parse the result.

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 the single node_type parameter already documents case/spaces/prefix optionality and gives an example, so the schema carries the parameter semantics. The description adds no further parameter detail, making the baseline 3 correct.

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 and resource ('Describes one node type: its parameters, curves and typed input/output pins'), clearly distinct from the sibling list_node_types which enumerates rather than inspects a single type. An agent can tell them apart without opening either schema.

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 instructs when to call it: before node_add/node_set to obtain valid parameter names, kinds, defaults and ranges, and before link_add to get pin names and data kinds. Alternative timing conditions are spelled out rather than left to inference.

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