IlluGen MCP

Overview Schema Source Related Servers Discussions Admin

Set curve

curve_set

DestructiveIdempotent

Replaces all keys of a node's curve in an IlluGen project to remap curves or define custom oscillator waveforms; writes the project file in place.

Instructions

Replaces all the keys of a node's curve (remap curves, custom oscillator waveforms...).

The previous keys are discarded. Writes the project file in place.
Returns: curve (name written) and keys (number of keys).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "path": "<path>",
      "node_id": "<node_id>",
      "curve": "<curve>",
      "points": "<points>"
    },
    "name": "curve_set"
  }
}

Input Schema

Name	Required	Description	Default
`path`	Yes	Absolute path of the .illugen project file.
`curve`	Yes	Curve name as shown by node_get or describe_node_type, e.g. Noise 'Final remap', Levels 'Main remap', Oscillator 'custom_waveform'.
`graph`	No	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).
`points`	Yes	At least 2 keys: [[position, value], ...] (positions usually 0..1), or dicts {position, value, interpolation} to vary the interpolation per key.
`node_id`	Yes	Node id as a string (from project_summary or node_add), or the node's label if it is unique.
`interpolation`	No	Interpolation for keys that do not set their own.	smooth

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedv0.1.2Oct 15, 2026

addedInput schema / properties / curve / description

Added value: +"Curve name as shown by node_get or describe_node_type, e.g. Noise 'Final remap', Levels 'Main remap', Oscillator 'custom_waveform'."

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 / interpolation / description

Added value: +"Interpolation for keys that do not set their own."

addedInput schema / properties / interpolation / enum

Added value: +[
+  "smooth",
+  "linear",
+  "constant",
+  "bezier"
+]

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 / points / description

Added value: +"At least 2 keys: [[position, value], ...] (positions usually 0..1), or dicts {position, value, interpolation} to vary the interpolation per key."

First observedv0.1.0Oct 15, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description adds real value beyond them: it spells out that previous keys are discarded and that the project file is written in place. That in-place write disclosure is exactly the kind of context annotations cannot convey.

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 tight lines: the destructive replacement is front-loaded, followed by the file-write consequence and a clearly labeled Returns line. No sentence is redundant.

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 no output schema present, the description correctly supplies the return shape (curve name and key count), plus the destruction and in-place write behavior. It stops short of stating whether the target curve must pre-exist or how errors on invalid positions are reported, which would matter for a destructive write.

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%, including enum values, defaults, and the points format, so the schema does the heavy lifting and a baseline of 3 applies. The description adds only the loose framing of 'keys' and the return field names; it contributes no semantics beyond the schema for path, graph, node_id, points, or interpolation.

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?

States a specific verb and resource: replacing all keys of a node's curve, with concrete examples (remap curves, custom oscillator waveforms). It is clearly distinguishable from generic node_set, though it never explicitly names the analogous siblings gradient_set/spline_set, so the agent must infer the routing.

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 is implied by the examples of curve types it targets, and 'replaces all the keys' hints that this is the wholesale-set operation rather than an incremental edit. However, there is no explicit when-to-use vs. gradient_set/spline_set/node_set guidance, and no prerequisite (e.g. curve must already exist) is stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.