Skip to main content
Glama
dokaNc

IlluGen MCP

by dokaNc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Screenshot project

project_screenshot
Read-onlyIdempotent

Open an .illugen project in an invisible IlluGen instance and capture its viewport and node graph as a PNG, so you can visually inspect graphs or diagnose render failures without altering the file.

Instructions

Opens the project in a private, invisible IlluGen and returns a screenshot of its window.

Shows the viewport and the node graph with each node's live preview: use it to check visually what a graph
does, or to see why a render fails. Use project_render to produce the actual image files. Works on a temporary
copy, so the project file is not modified. Needs IlluGen installed; takes a few seconds.
Returns {path} and a PNG image.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesAbsolute path of the .illugen project file.
widthNoWidth of the invisible IlluGen window, in pixels.
heightNoHeight of the invisible IlluGen window, in pixels.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.1.2
    • addedInput schema / properties / height / description
      Added value: +"Height of the invisible IlluGen window, in pixels."
    • addedInput schema / properties / path / description
      Added value: +"Absolute path of the .illugen project file."
    • addedInput schema / properties / width / description
      Added value: +"Width of the invisible IlluGen window, in pixels."
  2. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare a safe read-only, idempotent, non-destructive profile, but the description adds substantial context beyond them: the tool opens a private/invisible instance, operates on a temporary copy so the project file is not modified, requires IlluGen installed, and takes a few seconds. It also discloses the return shape ({path} and PNG).

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-loads the purpose and keeps use cases, alternative, side-effect guarantee, requirement, and return value in tight sentences. Slightly dense with parenthetical detail, but every sentence earns its place.

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?

Although there is no output schema, the description states the return value ({path} plus a PNG image). Combined with the requirement (IlluGen installed) and the non-destructive guarantee, an agent has everything needed to call this correctly.

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 path, width, and height are fully documented in the schema itself. The description adds no syntax or format detail about the parameters 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 ('returns a screenshot of its window') and immediately scopes the output ('viewport and the node graph with each node's live preview'). It is clearly distinguishable from siblings project_render and project_thumbnail by naming what is captured and why.

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 gives when-to-use ('check visually what a graph does, or to see why a render fails') and names the alternative for a different goal ('Use project_render to produce the actual image files'). Nothing is left to inference about choosing between them.

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