Skip to main content
Glama

banner_text

Render a short phrase as large block letters for headlines or title cards, with optional Unicode or ASCII fill and stacked rows.

Instructions

Render a short phrase as big block letters — display type, the way shape_text and the diagram tools each turn meaning into a picture. Give it text and it lays out each character as a 5-row glyph (A-Z, 0-9, space, and a little punctuation); lowercase is upper-cased. Use \n to stack multiple banner rows. Great for a headline atop a piece or a title card. style picks the ink charset (unicode solid block or ascii #); fill overrides it with any character.

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

Input Schema

NameRequiredDescriptionDefault
xNo
yNo
gapNoBlank columns between letters.
fillNoExplicit ink character; overrides `style`.
textYesThe phrase to enlarge. Use \n to stack multiple banner rows.
styleNoInk charset: unicode (solid block) or ascii (#).unicode

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose content limits (A-Z, 0-9, space, limited punctuation, lowercase upper-cased, 5-row glyphs), but it never says whether the banner is drawn onto a canvas at x/y or returned as text, nor anything about permissions, side effects, or how it interacts with siblings like clear_canvas or save_to_gallery.

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?

Front-loaded with the core action and the glyph constraint, and every sentence carries at least one fact (glyph set, \n stacking, style/fill relationship). The shape_text/diagram analogy is decorative and costs a few words without adding routing value.

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

Completeness2/5

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

For a 6-parameter rendering tool with no annotations and no output schema, the description leaves two real gaps: whether the result is drawing on a canvas or a returned string, and what `x`/`y` position the banner at. Content constraints are well covered, but the call-vs-mutate question an agent needs answered is not.

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 67%, so the baseline is 3. The description explains `text` (including \n stacking), `style` (unicode vs ascii ink), and `fill` overriding `style`, but `x`, `y`, and `gap` are left to the schema entirely, so it adds only modest meaning beyond structured fields.

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 ('Render a short phrase as big block letters') plus the output form: each character as a 5-row glyph. It also names shape_text and the diagram tools as kindred-but-distinct operations, so an agent can place this tool without opening the schema.

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?

Offers a positive use case ('headline atop a piece or a title card'), which implies when to reach for it. However, the mention of shape_text and the diagram tools is analogy rather than routing — it never states a condition under which an agent should pick one of those instead of banner_text.

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