Skip to main content
Glama

shape_text

Turns a poem or phrase into a calligram by packing its words into a builtin silhouette or an image-derived outline, so the text itself forms the picture.

Instructions

Pack a poem or phrase into a silhouette so the words themselves form the picture — a calligram. Give it text plus either a builtin shape (circle, heart, diamond, star, butterfly, triangle, tree, arrow) or an image path whose subject becomes the outline. The words trace the shape; by default the text repeats to fill it, and tall shapes like tree and arrow default to an upright silhouette (canopy + word-trunk). Set outline to wrap the figure in a crisp braille contour drawn at sub-pixel resolution while the words fill the body. This is the one-call way to make structured typographic illustrations.

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": {
      "text": "<text>"
    },
    "name": "shape_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
xNo
yNo
pathNoImage file whose subject becomes the silhouette. Provide this or `shape`.
textYesThe words to pour into the shape (a poem, a phrase).
shapeNoA builtin silhouette. Provide this or `path`.
widthNoSilhouette width in characters.
heightNoSilhouette height. Defaults from the shape's natural aspect (round shapes ~width/2, tree/arrow taller).
invertNoImage mask only: treat bright cells as the subject instead of dark ones.
repeatNoLoop the text to fill the whole shape. Off = write it once, then stop.
justifyNoHow each row fills its span: full block-justifies words edge to edge (densest, default); center or left keep single spacing.full
outlineNoTrace the silhouette's edge with fine braille dots (sub-pixel resolution) while the interior fills with text.
thresholdNoImage mask only: luminance cutoff — cells darker than this are inside the shape.

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 does real work: it discloses that text repeats by default to fill the shape, that tall shapes like `tree` and `arrow` default to an upright silhouette with a word-trunk, and that `outline` uses sub-pixel braille contouring. It does not say what gets written where (canvas placement via the undocumented x/y), whether existing content is overwritten, or what the call returns, leaving a notable gap for a render-style tool.

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 concept is front-loaded in the first clause, and each following sentence adds a distinct capability (shape vs image source, repeat default, outline). It is slightly longer than needed and leans on marketing phrasing like 'crisp braille contour drawn at sub-pixel resolution,' but no sentence is filler.

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

Completeness3/5

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

For a 12-parameter renderer with no annotations and no output schema, the description covers the creative behavior well but omits the operational picture: canvas placement, whether it draws over existing content, and what the result is. An agent could produce good-looking calligrams but would have to guess about composition with siblings like new_canvas, clear_canvas, or render.

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 83%, so the baseline is 3 and the schema already explains most parameters well. The description adds some genuine meaning — notably which shapes are tall and how `repeat`/`justify` interact with fill — but it says nothing about `x`/`y` (the one pair the schema leaves bare), so it does not fully compensate where the schema is thin.

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 pairs a specific verb with a concrete artifact: 'Pack a poem or phrase into a silhouette... a calligram,' and immediately names the two input routes (builtin `shape` vs image `path`). That distinguishes it cleanly from siblings like draw_text, banner_text, and illustrate, which an agent can rule out without opening other schemas.

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 states the invocation condition plainly — supply `text` plus either a builtin `shape` or an image `path` — and positions the tool as 'the one-call way to make structured typographic illustrations,' which implicitly contrasts it with multi-call composition approaches. There is no explicit 'when not to use this' or named sibling alternative, so it stops short of a 5.

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