Skip to main content
Glama

illustrate_prompt

Turn a short phrase into deterministic blog-style vector art: maps keywords to motifs, colors, line styles, layout, and backdrop, saves SVG/PNG, and reports the interpretation.

Instructions

Turn a short natural-language phrase into blog-style vector art by DETERMINISTICALLY mapping its words to a motif (or several), an accent hue, a line style, a layout, and a backdrop — then drawing them with the procedural engine. This is plain keyword + synonym matching (no model, offline, reproducible per phrase), so keep the phrase concrete and name the thing(s) to draw: e.g. "a rough sketch of a brain and a blue spark on dark", "gear, spark and atom in a grid", "a bold clean magnifier". Two or more motifs compose into one plate; grid/row/column/scatter (and cues like "next to", "stacked", "scattered") set the layout; colour words or a #rrggbb set the accent; "rough"/"clean"/"bold"/"thin"/"sketchy" restyle the line; "on dark", "transparent", or "no accent" change the backdrop. Returns the art plus a readback of what it understood, and writes .svg/.png to mcp/out/ (standalone — never the ASCII gallery). For exact motif names and full control, use illustrate / illustrate_scene.

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": {
      "prompt": "<prompt>"
    },
    "name": "illustrate_prompt"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoBase filename for the saved files (default: the motif name).
seedNoOverride the wobble seed (default: a stable hash of the phrase).
sizeNoOutput size in pixels (square).
promptYesA short phrase naming what to draw, e.g. "a rough brain and a blue spark on dark".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses determinism (plain keyword/synonym matching, offline, reproducible per phrase), the return payload (art plus a readback of what it understood), and the side effect of writing .svg/.png to mcp/out/ rather than the ASCII gallery. It stops short of stating what happens when no motif matches or whether existing files at the same `name` are overwritten.

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?

The core action and the determinism caveat are front-loaded, and the grammar-cue sentence is dense but each clause maps to a real capability. It is somewhat overloaded with em-dashes and inline examples, which makes it heavier to scan than necessary.

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 a 4-parameter tool with full schema coverage and no output schema, the description covers purpose, input grammar, determinism, return value, and file-write location — enough to call it correctly. Only edge behavior (no-match phrases, filename collisions) is left unstated.

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 coverage is 100%, so the baseline is 3; the description earns an extra point by explaining how the `prompt` string is actually parsed — motif words, `grid`/`row`/`column`/`scatter` layout cues, colour words or #rrggbb, line-style adjectives, and backdrop phrases. It adds no meaning for `name`, `seed`, or `size` beyond what the schema already documents.

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: turning a short natural-language phrase into blog-style vector art via deterministic keyword mapping plus procedural drawing. It also distinguishes itself from siblings by positioning itself as the phrase-level convenience layer versus `illustrate`/`illustrate_scene` for exact motif control.

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 tells the agent how to use it (keep the phrase concrete, name the thing(s) to draw) with three concrete example phrases, and names the alternatives (`illustrate`, `illustrate_scene`) along with the condition that selects them (exact motif names and full control).

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