Skip to main content
Glama

illustrate

Generate flat, hand-inked two-tone vector spot illustrations from a builtin motif, returning both SVG source and a PNG preview saved to disk.

Instructions

Draw real two-tone VECTOR art in the flat, hand-inked style of blog-style spot illustrations — filled organic shapes, no outlines, a strict ink/cream/clay palette. This is a PURE art generator that returns an SVG plus a PNG preview; it is standalone and does NOT touch the ASCII canvas or the gallery. Pick a builtin motif (spark, chat, magnifier, cube, gear, heart, key, bricks, city, bolt, leaf, eye, star, microphone, terminal, brain, head, prism, atom, node, grid, link, fanout, chip, beam, burst, mesh, prompt, window, braces, cursor, folder, document, commit, bug, stack, cloud, person, hand, foot, bone, ribcage, lungs, tooth, muscle, pulse, kidney, circuit, neuron, layers, database, binary, signal, radar, token, vision, compass, pill, tablet, syringe, flask, dna, cross, stethoscope, microscope, bandage, molecule, robot, android, arm, gripper, rover, drone, antenna, battery, sensor, nut, sun, moon, mountain, tree, flame, droplet, wave, planet, snowflake, rainbow, barchart, linechart, piechart, gauge, histogram, funnel, meter, trend, scatterplot, candles, balance, golem, alien, octopus, ship, boat, lighthouse, anchor). The PNG renders inline so you can see it; the SVG source is returned as text; both are written to mcp/out/. size is the pixel size; accent toggles the highlight; accentColor picks its hue (clay, rust, red, blue, pink, yellow, green, slate, or a #rrggbb); background is paper (cream), none (transparent), or ink (dark); seed reshuffles the hand-drawn wobble; invert makes it light-on-dark; roughness/weight/sketch restyle the drawn line from clean and geometric to loose, and thin to bold.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "motif": "<motif>"
    },
    "name": "illustrate"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoBase filename for the saved files (defaults to the motif name).
seedNoDeterministic seed for the hand-drawn wobble (motifs only).
sizeNoOutput size in pixels (square for motifs).
motifYesWhich builtin motif to draw.
accentNoDraw the accent shapes at all (motifs only).
invertNoSwap ink and paper for light-on-dark art.
sketchNoMotifs only: a looser, sketchier hand (preset; roughness/weight override it).
weightNoMotifs only: ink line-thickness scale for the drawn strokes (default 1).
roughnessNoMotifs only: hand-drawn wobble scale — 0 clean/geometric, 1 default, up to 4 loose.
backgroundNoBackdrop: 'paper' cream, 'none' transparent, or 'ink' dark.paper
accentColorNoAccent hue (motifs only): a name (clay, rust, red, blue, pink, yellow, green, slate) or a #rrggbb. Defaults to clay.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and mostly meets it: it discloses the return payload (SVG text plus an inline PNG preview), the side effect of writing both files to mcp/out/, and that the operation is standalone and non-destructive. It omits whether files overwrite existing ones when `name` collides with a previous run, which matters for a file-writing tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening sentences are dense and correctly front-loaded — style, return type, and isolation boundary come before anything else. However, the middle of the description is a verbatim recitation of roughly 110 motif enum values that are already in the schema, which bloats the definition substantially without adding information an agent can act on.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 11-parameter generator with no annotations and no output schema, the description covers what an agent needs: what is produced, where it lands, and the visual effect of the styling parameters. The remaining gaps — the `name` parameter and overwrite semantics — are minor because the schema documents `name` directly.

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%, so the baseline is 3 and the schema already documents every parameter including ranges and defaults. The description adds some qualitative meaning the numbers cannot convey ('roughness/weight/sketch restyle the drawn line from clean and geometric to loose, and thin to bold'), but it also spends most of its parameter prose restating enum values already in the schema, and it never mentions the `name` parameter at all.

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?

The description names a specific verb and output ('Draw real two-tone VECTOR art'), pins the visual style ('flat, hand-inked ... filled organic shapes, no outlines'), and explicitly separates the tool from the canvas/gallery siblings. An agent can tell this is a standalone raster/SVG illustration generator, not an ASCII-canvas drawing primitive.

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?

It gives a clear negative boundary — 'standalone and does NOT touch the ASCII canvas or the gallery' — which rules out draw_block, draw_icon, save_to_gallery and friends. What it does not do is differentiate from the nearest siblings, illustrate_prompt and illustrate_scene, which an agent would most plausibly confuse it with; no when-to-use-for-which alternative is stated.

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