Skip to main content
Glama
dokaNc

IlluGen MCP

by dokaNc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Render project

project_render
Idempotent

Renders an IlluGen project by exporting every enabled Node_Export node to image files, without modifying the project or disturbing your open IlluGen instance.

Instructions

Renders the project with the real IlluGen: runs the export of every enabled Node_Export_* node.

IlluGen runs as a private, invisible instance (an IlluGen open on screen is not affected). The project file
itself is not modified; image files are written to output_dir or to the export nodes' folders, overwriting
files with the same names. Needs IlluGen installed and at least one enabled export node. Run project_validate
first when the graph is new.
Returns: a result {ok, items_written, seconds, files (written paths), exports (settings of each export node),
log_issues} followed by a preview image. On failure: {ok: false, error, log_issues, hint} plus screenshots of
IlluGen's error dialogs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesAbsolute path of the .illugen project file.
previewNoAttach a downscaled preview of the first exported image.
timeout_sNoMaximum time to wait for the export, in seconds.
output_dirNoAbsolute folder to write every export to (created if needed). Empty = the folders set on the export nodes, usually next to the project.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.1.2
    • addedInput schema / properties / output_dir / description
      Added value: +"Absolute folder to write every export to (created if needed). Empty = the folders set on the export nodes, usually next to the project."
    • addedInput schema / properties / path / description
      Added value: +"Absolute path of the .illugen project file."
    • addedInput schema / properties / preview / description
      Added value: +"Attach a downscaled preview of the first exported image."
    • addedInput schema / properties / timeout_s / description
      Added value: +"Maximum time to wait for the export, in seconds."
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the annotations: discloses that IlluGen runs as a private invisible instance, that the project file is not modified, that image files are written and existing files with the same name are overwritten, and that failures yield screenshots of error dialogs. This is exactly the mutation/overwrite context the annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=true) cannot convey on their own.

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?

Front-loaded with the core action, then structured into behavior, requirements, and return shape. Dense but every sentence carries information; only mild redundancy with the schema on output_dir.

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?

No output schema exists, and the description fully covers the return contract: success shape ({ok, items_written, seconds, files, exports, log_issues} plus preview) and failure shape ({ok: false, error, log_issues, hint} plus screenshots). Nothing an agent needs to invoke or interpret results 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 the schema already documents path, preview, timeout_s, and output_dir. The description restates output_dir behavior ('written to output_dir or the export nodes' folders') but adds no syntax or format detail beyond what the schema provides; 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?

States a specific verb (renders/runs export) and resource (the project's enabled Node_Export_* nodes) and implicitly distinguishes itself from project_validate, project_screenshot, and project_thumbnail. An agent can tell exactly what operation this performs 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 Guidelines4/5

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

Gives clear prerequisites (IlluGen installed, at least one enabled export node) and an explicit sequencing rule: 'Run project_validate first when the graph is new.' It does not, however, state when to prefer project_render over project_thumbnail/project_screenshot, so it stops short of naming alternatives.

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