Skip to main content
Glama
dokaNc

IlluGen MCP

by dokaNc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Set spline points

spline_set
DestructiveIdempotent

Replace control points for spline, sweep, point-shape, or lattice nodes in an IlluGen project file, overwriting existing points; optional edges define branching.

Instructions

Replaces the control points of a spline, sweep, point-shape or lattice node.

Points are chained in order unless `edges` is given. The previous points are discarded. Fails if the node has
no spline or lattice points. Writes the project file in place.
Returns: points (number written) and edges (number of segments, when applicable).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesAbsolute path of the .illugen project file.
edgesNoOptional explicit segments [[i, j], ...] between point indexes, for branching shapes. Overrides the default chaining.
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).
closedNoConnect the last point back to the first (closed shape).
pointsYesControl points in order: [x, y, z] in scene units for Grayscale_Spline, Geometry_Sweep and Geometry_Points_Shape; [x, y] in 0..1 for Utils_Lattice.
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. Changed6 schema fields changedv0.1.2
    • addedInput schema / properties / closed / description
      Added value: +"Connect the last point back to the first (closed shape)."
    • addedInput schema / properties / edges / description
      Added value: +"Optional explicit segments [[i, j], ...] between point indexes, for branching shapes. Overrides the default chaining."
    • 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."
    • addedInput schema / properties / points / description
      Added value: +"Control points in order: [x, y, z] in scene units for Grayscale_Spline, Geometry_Sweep and Geometry_Points_Shape; [x, y] in 0..1 for Utils_Lattice."
  2. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Goes beyond the annotations by disclosing that previous points are discarded, that the operation fails on nodes without spline/lattice points, that it writes the project file in place, and what it returns (point and segment counts). The discard behavior corroborates destructiveHint=true and the return info substitutes for a missing output schema.

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?

Four short sentences, each carrying a distinct fact: what is replaced, default versus explicit chaining, failure and side-effect behavior, and return values. The most important clause (replacement) is front-loaded 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?

For a destructive mutation tool with full schema coverage and no output schema, the description supplies the write-in-place side effect, failure mode, and return shape. It stops short of stating permission/auth requirements or interaction with the `graph` scoping, which would round it out.

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%, so all six parameters are already documented, including point formats per node type and the edges override. The description's chaining statement largely restates the schema's 'Overrides the default chaining' note, so it adds little beyond the baseline.

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+resource ('Replaces the control points of a spline, sweep, point-shape or lattice node') and enumerates the node types it applies to. It does not differentiate itself from the neighboring curve_set or node_set, so an agent must infer when spline_set is the right choice.

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?

Gives a usage condition for `edges` ('chained in order unless edges is given') and a precondition ('Fails if the node has no spline or lattice points'). However it never contrasts this tool with curve_set, gradient_set, or node_set, so selection among siblings is left to the agent's 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