Skip to main content
Glama

add_outline

Outline a sprite on a transparent background, like the Sprite Outline tool on voidless.dev/tools: colour, thickness, outside (the canvas grows by thickness + 2 px a side, as on the site, unless expand is false) or inside (the sprite's own edge pixels), 8-connected (rounded) or 4-connected (blocky) corners. Images up to 2048x2048, 256 frames, 32 MB of input per call. Free: no credits.

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": {
      "image": "<image>"
    },
    "name": "add_outline"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNooutside
saveNoAlso save the result to your Voidless library (free, private) and return its asset id and cdn.voidless.dev URL, for passing to the next tool without base64
colorNoHex, #rrggbb or #rrggbbaa#000000
imageYesAn image: an https URL (e.g. a cdn.voidless.dev link from get_asset or a saved result), a library image key (assets/…png, as get_asset lists it), a data: URI, or base64 PNG/GIF.
expandNoOutside only: grow the canvas so the outline fits
thicknessNo
connectivityNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare openWorldHint=true and destructiveHint=false, and the description adds genuinely useful context beyond them: hard limits (2048x2048, 256 frames, 32 MB input per call), the cost model ("Free: no credits"), and the precise canvas-growth rule for outside mode with expand. It does not state what the call returns (image bytes vs. URL) or behavior on failure, which is the remaining gap.

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

Conciseness5/5

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

One dense but front-loaded sentence plus two short clauses; the operation, modes, limits, and pricing each appear exactly once with no filler. Nothing could be removed without losing actionable information.

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 7-parameter image-mutation tool with no output schema, the definition covers constraints, cost, and parameter meanings well, but never says what comes back — base64 image, URL, or asset id — so the agent cannot plan a chained call without guessing. The save parameter hints at a URL path, but the default return shape remains undocumented.

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?

With schema coverage at 57%, mode, thickness, and connectivity have no schema descriptions, and the description compensates well: outside vs. inside is explained concretely (canvas grows by thickness + 2 px per side vs. the sprite's own edge pixels), and 8-connected vs. 4-connected is glossed as rounded vs. blocky corners. Color and expand are only partly elaborated, but the ambiguous parameters are well covered.

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 ("Outline a sprite on a transparent background") and anchors it to a known reference implementation (Sprite Outline on voidless.dev/tools). No sibling in the list (clean_up_sprite, resize_sprite, rotate_sprite, etc.) could be confused with this operation, so the agent can disambiguate immediately.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the agent can infer this is an edge-outlining step in a sprite pipeline, but there is no explicit "use this when X, use Y instead" guidance or statement of prerequisites. With 45 sibling tools including adjacent image-mutation tools, a sentence pointing to alternatives (e.g. clean_up_sprite, resize_sprite) would materially help.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources