IlluGen MCP

by dokaNc

Overview Schema Source Related Servers Discussions Admin

Python

Local

List presets

list_presets

Read-onlyIdempotent

Browse IlluGen presets, then pass a name to create an editable project copy; filter by name text. Read-only.

Instructions

Lists the example projects shipped with IlluGen, usable as starting points.

Pass a returned name to project_new(from_preset=...) to get an editable copy; the presets themselves are
never modified. Read-only; reads the presets folder of the installed IlluGen.
Returns [{name, path}], sorted by name. The list is empty when nothing matches or when IlluGen is not found
(check illugen_status).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`search`	No	Keep only presets whose name contains this text (case-insensitive). Empty = all presets.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.1.2Oct 15, 2026

addedInput schema / properties / search / description

Added value: +"Keep only presets whose name contains this text (case-insensitive). Empty = all presets."

First observedv0.1.0Oct 15, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive). The description adds real behavioral context beyond them: the data source (presets folder of the installed IlluGen), the guarantee that presets are never modified, and the two conditions that produce an empty result.

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 purpose, then follow-up usage, then return/empty-case behavior. Nearly every sentence earns its place, though the trailing parenthetical about illugen_status could be tightened.

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?

Covers purpose, next-step workflow, return shape, sorting, and the empty-result condition, which is everything an agent needs for a one-parameter read tool. An output schema exists, so the brief return description is a bonus rather than a requirement.

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% and the single 'search' parameter is fully documented in the schema (case-insensitive substring match, empty = all). The description adds no parameter-level detail 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?

States a specific verb and resource ('Lists the example projects shipped with IlluGen') plus their purpose ('usable as starting points'). An agent can immediately distinguish this read-only catalog from mutation siblings like project_new.

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?

Explicitly routes the agent: pass a returned name to project_new(from_preset=...) to get an editable copy, and check illugen_status when the list comes back empty. Both the follow-up action and the empty-result fallback are named, leaving nothing to inference.

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