Skip to main content
Glama
dokaNc

IlluGen MCP

by dokaNc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Project settings

project_set_settings
Idempotent

Set project-wide animation settings like frame rate, loop region, and default texture size. Only specified values change; omitted ones persist, and the .illugen file is updated in place.

Instructions

Changes project-wide settings: frame rate, animation loop region and default texture size.

Only the values you pass change; omitted ones are kept. Applies to the whole project (top-level graph and
subgraphs). Writes the project file in place. The resolution of an individual export is set on its export
node with node_set.
Returns the resulting settings, same shape as project_summary.settings.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesAbsolute path of the .illugen project file.
loop_regionNo[start, end] of the animation loop, in seconds (e.g. [0, 2] = 2 s, 120 frames at 60 fps).
frames_per_secondNoAnimation frame rate, e.g. 30 or 60.
default_texture_widthNoDefault texture width, a power-of-two enum string from '_1' to '_16384', e.g. '_512', '_1024', '_2048'.
default_texture_heightNoDefault texture height, same values as default_texture_width.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.1.2
    • addedInput schema / properties / default_texture_height / description
      Added value: +"Default texture height, same values as default_texture_width."
    • addedInput schema / properties / default_texture_width / description
      Added value: +"Default texture width, a power-of-two enum string from '_1' to '_16384', e.g. '_512', '_1024', '_2048'."
    • addedInput schema / properties / frames_per_second / description
      Added value: +"Animation frame rate, e.g. 30 or 60."
    • addedInput schema / properties / loop_region / description
      Added value: +"[start, end] of the animation loop, in seconds (e.g. [0, 2] = 2 s, 120 frames at 60 fps)."
    • addedInput schema / properties / path / description
      Added value: +"Absolute path of the .illugen project file."
  2. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

With annotations already declaring non-read-only, non-destructive and idempotent, the description adds the meaningful extras: it writes the project file in place, applies to the whole project including subgraphs, and performs a partial merge of supplied values only. That is real behavioral context beyond the hints, though it omits any mention of permissions or failure modes.

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, zero filler. Purpose and merge semantics come first, scope second, the sibling disambiguation and return-value note last — the ordering matches how an agent reads the tool.

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?

Even without an output schema, the description closes the loop by stating the return is the resulting settings in the same shape as project_summary.settings. Scope, partial-update behavior and the write-in-place effect are all covered for a 5-parameter mutation 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 parameter formats (seconds, fps, power-of-two enum strings) are already fully documented in the schema. The description only restates the field groups at a high level, adding scope rather than meaning, which is the expected baseline when the schema carries the load.

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 (changes) and resource (project-wide settings) and enumerates the three affected settings groups. It also explicitly distinguishes itself from node_set, which handles per-export resolution, so an agent can separate the two 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 Guidelines4/5

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

Gives the key selection condition ('only the values you pass change; omitted ones are kept') and routes a related but distinct need (per-export resolution) to node_set. It stops short of naming when to prefer project_new or project_normalize, so it is clear context without full exclusion rules.

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