Skip to main content
Glama
dokaNc

IlluGen MCP

by dokaNc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Set raw node data

node_set_data
DestructiveIdempotent

Overwrites one raw field in a node's internal data block for fields other setters miss, writing without type checking; run project validation afterward.

Instructions

Low-level escape hatch: overwrites one raw field of a node's internal data block.

Use it only for fields that node_set, curve_set, gradient_set and spline_set do not cover. The value is
written without type checking, so run project_validate(engine=true) afterwards. Writes the project file in
place.
Returns {"ok": true}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYesName of an existing field of the node's data block. An unknown name fails and lists the available fields.
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).
valueYesNew value as tagged JSON, in the same form node_get uses: vectors as {"__vec__": "f3", "v": [x, y, z]}.
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. Changed7 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 / key / description
      Added value: +"Name of an existing field of the node's data block. An unknown name fails and lists the available fields."
    • 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."
    • addedInput schema / properties / value / description
      Added value: +"New value as tagged JSON, in the same form node_get uses: vectors as {\"__vec__\": \"f3\", \"v\": [x, y, z]}."
    • changedInput schema / properties / value / title
      Previous value: -"value"New value: +"Value"
    • removedInput schema / properties / value / type
      Removed value: -"string"
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, and the description reinforces this with concrete consequences: the value is written without type checking, the project file is written in place, and validation should be run afterwards. It also discloses the return shape, which no output schema provides.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences that are tightly front-loaded: purpose first, then the when-not-to-use constraint, then the risk/validation notice and return value. No sentence is 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 no output schema, the description supplies the return value, the side effect (in-place project file write), the validation requirement, and the sibling alternatives. Nothing needed to invoke it safely is missing.

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 key, path, graph, value and node_id are all documented in the schema, including the tagged-JSON value format and the unknown-key failure mode. The description adds no meaning beyond that, so the baseline 3 applies.

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?

The description states a precise verb and resource ('overwrites one raw field of a node's internal data block') and frames it as a low-level escape hatch, which immediately distinguishes it from the higher-level setters. An agent can tell what this does without opening the 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?

It explicitly limits use to fields not covered by node_set, curve_set, gradient_set and spline_set, naming the alternatives and the condition that selects this tool over them. It also prescribes a follow-up step (project_validate) after use.

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