Skip to main content
Glama

restyle_ascii

Re-skin an existing ASCII drawing with a different character palette by remapping glyphs to matching-density characters, blocks, braille, or custom substitutions while preserving the picture.

Instructions

Re-skin an existing ASCII drawing with a different character palette. Drop in text (or a path to a .txt, or use the current canvas) and it swaps every glyph for the matching-darkness character in a target ramp — turning #%@ art into shade blocks (░▒▓█), braille tone, or any custom ramp, while keeping the picture. Or give an explicit map of char->char substitutions for full control. The result replaces the canvas so you can render or save it.

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

Input Schema

NameRequiredDescriptionDefault
mapNoExplicit source-char -> target-char substitutions. When given, replaces the density remap.
pathNoPath to a .txt file to restyle. Used when `text` is omitted.
rampNoCustom target ramp, empty -> full ink. Overrides `ramp_preset`.
textNoThe ASCII art to restyle. If omitted, uses `path`, else the current canvas.
invertNoFlip light<->heavy for drawn glyphs; background spaces stay blank.
ramp_presetNoTarget palette: 'blocks' = ░▒▓█, 'braille' = fine tone, 'classic'/'jp2a' = density letters. Ignored if `ramp` or `map` is given.blocks

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.9/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 well: it discloses the key side effect ('The result replaces the canvas so you can render or save it') and that the picture is preserved while glyphs change. It doesn't cover permissions, reversibility, or return shape, but the canvas-mutation disclosure is the critical one for this 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?

Three front-loaded sentences that move purpose → input options → output effect in a logical order, with no filler. The parenthetical asides are slightly dense but each 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 6-parameter, zero-required tool with no output schema, the description covers input sourcing, the transformation, and where the result lands. The only meaningful gap is that return/output behavior is only gestured at via 'so you can render or save it'.

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 coverage is 100%, so precedence rules (map > ramp > ramp_preset, text > path > canvas) are already documented in the schema. The description narrates the same fallback chain and map-vs-ramp choice but adds little technical detail beyond it, making 3 the appropriate baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb+resource ('Re-skin an existing ASCII drawing with a different character palette') and illustrates the transform with concrete examples ('#%@' art into shade blocks ░▒▓█, braille, custom ramps). It's clearly distinct from convert-from-image tools, though it never explicitly names a sibling or draws the boundary with image_to_ascii/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 clearly explains the source options (explicit `text`, a `path` to a .txt, or the current canvas) and presents `map` as the full-control alternative to density remapping. It gives solid context for how to invoke it but no explicit when-not guidance or named alternatives outside itself.

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