Skip to main content
Glama
dokaNc

IlluGen MCP

by dokaNc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

New project

project_new

Creates a new .illugen project file, blank or copied from a preset/project, returning the path and summary so you can add nodes with node_add.

Instructions

Creates a new .illugen project file, blank or copied from a preset or another project.

Start every new graph here, then add nodes with node_add. Writes only the file at `path`; the copied preset
or project is left untouched, and a copied preset is made editable.
Returns the new file's path plus its summary (same shape as project_summary).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesAbsolute path of the project to create; must end in .illugen. Missing folders are created.
overwriteNoReplace the file if it already exists (its previous content is lost). Default false: fail instead.
from_presetNoOptional source to copy: a preset name from list_presets, or an absolute path to any .illugen file. Empty = blank project.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.1.2
    • addedInput schema / properties / from_preset / description
      Added value: +"Optional source to copy: a preset name from list_presets, or an absolute path to any .illugen file. Empty = blank project."
    • addedInput schema / properties / overwrite / description
      Added value: +"Replace the file if it already exists (its previous content is lost). Default false: fail instead."
    • addedInput schema / properties / path / description
      Added value: +"Absolute path of the project to create; must end in .illugen. Missing folders are created."
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Goes beyond the annotations by disclosing the write scope ('Writes only the file at `path`; the copied preset or project is left untouched, and a copied preset is made editable') and by describing the return payload. Annotations cover the readOnly/destructive profile, so this added mutation-scope detail is genuine value rather than repetition.

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 sentences, each earning its place: the action leads, the workflow hint follows, then the side effects and return shape. No filler or restatement of the title.

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?

Though there is no output schema, the description names the return value and cross-references project_summary for its shape, so an agent knows what to expect. Side effects, overwrite behavior, and the required path are all covered across description and schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3, but the description adds real meaning for `from_preset` by clarifying that a copied preset becomes editable and that the source is left untouched. `overwrite`'s destructive potential and `path` semantics are left to the schema, which already covers them.

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 ('Creates a new .illugen project file') plus the two creation modes (blank or copied from preset/project), which separates it cleanly from siblings like project_normalize or project_summary that operate on existing files. An agent can identify it 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?

'Start every new graph here, then add nodes with node_add' gives an explicit ordering and points at the next tool in the workflow. It doesn't state when NOT to use it (e.g. use project_normalize for existing files), but the creation framing makes the boundary largely self-evident.

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