Skip to main content
Glama

draw_icon

Stamp clean two-tone braille pictographic icons onto a canvas from built-ins or trace SVG/PNG art for bullets, badges, or header marks.

Instructions

Stamp a clean pictographic icon onto the canvas as high-resolution Unicode braille line-art, in the flat, two-tone, hand-inked spirit of the Claude blog's spot illustrations. Either pick a builtin name (arrow, bolt, bricks, chat, check, city, code, cube, gear, heart, key, magnifier, spark, star, terminal) or give an image path (SVG, PNG, ...) to trace any flat illustration or logo into the same braille-icon style — the blog's own art traces cleanly. size sets the width in cells (height auto). Filled shapes become solid ink, strokes stay fine lines. weight thickens the linework (scales the pen for a builtin, dilates thin strokes for a traced image); for a traced image, threshold sets the ink cutoff. invert flips ink/paper (use it for light-on-dark art). Great as a bullet, a badge, a header mark, or a motif beside a title.

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": "draw_icon"
  }
}

Input Schema

NameRequiredDescriptionDefault
xNo
yNo
nameNoWhich icon to draw from the builtin library. Provide this or `path`.
pathNoImage file (SVG/PNG/...) to trace into a braille icon. Provide this or `name`.
sizeNoIcon width in characters. Height is auto (a builtin reads square).
invertNoSwap ink and paper (draw as negative space, or trace light-on-dark art).
weightNoStroke thickness. Higher = bolder, inkier lines. For a builtin it scales the pen; for a traced image it dilates thin line art so it reads solid.
thresholdNoTraced image only: luminance cutoff — pixels darker than this become ink.
transparentNoLayer the icon over existing art (blank cells are skipped). Off = paste opaquely.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses rendering behavior ('Filled shapes become solid ink, strokes stay fine lines'), that `weight` behaves differently for builtins vs traced images, that `invert` is for light-on-dark art, and that transparent layering skips blank cells. It omits error behavior when neither `name` nor `path` is supplied and never mentions where on the canvas the icon lands (x/y).

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 content is front-loaded with purpose and mode selection before diving into parameter behavior, and the closing sentence adds legitimate use-case framing rather than filler. It is a single dense paragraph of roughly 120 words, so it is longer than strictly necessary but nearly every clause carries information.

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 nine-parameter, annotation-free tool with no output schema, the description covers the tricky parts (dual input modes, weight/threshold interaction, inversion, layering) that an agent could otherwise get wrong. The remaining gaps are canvas placement semantics and what happens on missing input, which the schema partially covers.

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 78%, so the baseline is already high, but the description adds real meaning: `size` is described as width in cells with auto height, `weight` is explained as scaling the pen for builtins versus dilating thin strokes for traces, and `threshold` is framed as an ink cutoff. Placement parameters (`x`, `y`) and `transparent` are left entirely to the schema.

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 opens with a specific verb and resource: 'Stamp a clean pictographic icon onto the canvas as high-resolution Unicode braille line-art.' It also pins down the visual style (flat, two-tone, hand-inked) and enumerates the builtin library, which clearly separates it from siblings like draw_block, draw_rect, or image_to_braille.

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 explicit mode selection ('either pick a builtin `name` ... or give an image `path`') and names concrete scenarios (bullet, badge, header mark, motif beside a title). It doesn't explicitly compare against siblings such as image_to_braille or draw_block, so an agent must infer when a full-image trace tool is preferable to this one.

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