Skip to main content
Glama

illustrate_scene

Compose multiple builtin motifs into a single blog-style vector plate, arranging them automatically or by exact placement, and export as SVG with a PNG preview.

Instructions

Compose SEVERAL builtin motifs into one blog-style vector PLATE — a single SVG (plus PNG preview) with each motif placed, scaled, and rotated in the flat ink/cream/clay language. Like illustrate, but for a whole arrangement. Give motifs (a list auto-arranged by layout: focal, grid, row, column, or scatter — focal is the default and reads best, a hero motif ringed by smaller satellites) for the quick path, or placements for exact control (each: motif + center x/y in 0..1000, scale, rotate, optional accent/accentColor/seed). Shared knobs: size, background (paper/none/ink), seed, invert, scene-wide accent/accentColor, roughness/weight/sketch line style, and pad (margin around auto cells). Standalone: writes to mcp/out/ and never touches the ASCII gallery. Motifs: 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.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "illustrate_scene"
  }
}

Input Schema

NameRequiredDescriptionDefault
padNoMargin kept around each auto-laid cell (default 0.14).
nameNoBase filename for the saved files (default 'scene').
seedNoDeterministic seed for wobble and scatter.
sizeNoOutput size in pixels (square).
accentNoScene-wide accent toggle (a placement can override).
invertNoSwap ink and paper for light-on-dark art.
layoutNoHow `motifs` are auto-arranged. `focal` (default) makes the first motif a large hero ringed by smaller satellites linked with thin spokes; grid/row/column/scatter place every motif at the same weight.focal
motifsNoMotifs to auto-arrange by `layout`. Provide this or `placements`.
sketchNoLooser, sketchier hand (preset).
weightNoInk line-thickness scale (default 1).
roughnessNoWobble scale — 0 clean, 1 default, up to 4 loose.
backgroundNoBackdrop: paper, none, or ink.paper
placementsNoExact placements. Provide this or `motifs`.
accentColorNoScene-wide accent hue (name or #rrggbb; default clay).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.4/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 disclose key side effects: it is standalone, writes files to mcp/out/, and never modifies the ASCII gallery. It also reveals determinism via `seed` and that output is SVG plus PNG preview. It stops short of stating whether files are overwritten on name collision or what errors look like.

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 core statement and the motifs-vs-placements fork are front-loaded well, and the 'Shared knobs' grouping is useful. However, the final ~110-item motif enumeration duplicates the schema enum verbatim and consumes a large share of the text without adding selection value, which blunts conciseness.

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 14-parameter tool with no annotations and no output schema, the description covers the essentials: output artifacts, write location, layout semantics, both input modes, and the style knobs. Only failure/overwrite behavior and inter-knob interactions (e.g., `sketch` vs `roughness`/`weight`) are left implicit.

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, but the description adds genuine meaning: it spells out the `focal` layout as 'a hero motif ringed by smaller satellites', explains `pad` as margin around auto cells, and enumerates the placement sub-fields with their 0..1000 coordinate space. It also states the motifs/placements either-or relationship, a constraint the schema itself does not express.

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 ('Compose SEVERAL builtin motifs into one blog-style vector PLATE — a single SVG plus PNG preview') and explicitly positions itself against the sibling: 'Like `illustrate`, but for a whole arrangement.' An agent can distinguish single-motif from multi-motif usage without opening either schema.

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?

Gives an explicit decision between two mutually exclusive input paths: `motifs` for the 'quick path' auto-arranged by `layout`, or `placements` for 'exact control'. It also recommends a default ('focal ... reads best') and clarifies scope ('never touches the ASCII gallery'), so the agent knows when this tool is and isn't the right one.

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