Skip to main content
Glama

John's Essentials

by com.johnsessentials
OverviewDiscussionsAdmin

generate_ascii_art

ASCII Art Generator — Convert text or an image to ASCII art. Mode 'text' (default) requires 'text'; mode 'image' requires 'file'. [category: generate]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fileNoThe picture to convert (max 10 MB).
fontNoLettering style.standard
modeNoDraw your words as big letters, or turn a picture into characters. If you attach a picture and type nothing, picture mode is used automatically.text
textNoThe words to draw. Longer than 100 characters is trimmed.
widthNoHow many characters wide the picture is.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedInput schema / properties / file / description
      Previous value: -"Image to convert. REQUIRED when mode=image (max 10MB)."New value: +"The picture to convert (max 10 MB)."
    • addedInput schema / properties / file / x-show-when
      Added value: +{
+  "mode": [
+    "image"
+  ]
+}
    • changedInput schema / properties / font / enum
      Previous value: -[
-  "standard",
-  "banner",
-  "big",
-  "block",
-  "bubble",
-  "digital",
-  "lean",
-  "mini",
-  "script",
-  "shadow",
-  "slant",
-  "small"
-]New value: +[
+  "standard",
+  "big",
+  "block",
+  "banner",
+  "bubble",
+  "digital",
+  "ivrit",
+  "lean",
+  "mini",
+  "mnemonic",
+  "script",
+  "shadow",
+  "slant",
+  "small",
+  "smscript",
+  "smshadow",
+  "smslant",
+  "term"
+]
    • changedInput schema / properties / mode / description
      Previous value: -"Turn words into a banner, or turn a picture into characters."New value: +"Draw your words as big letters, or turn a picture into characters. If you attach a picture and type nothing, picture mode is used automatically."
    • changedInput schema / properties / text / description
      Previous value: -"The words to render as a banner. Up to 100 characters."New value: +"The words to draw. Longer than 100 characters is trimmed."
    • changedInput schema / properties / width / description
      Previous value: -"How many characters wide the picture is drawn."New value: +"How many characters wide the picture is."
  2. Changed8 schema fields changed
    • changedInput schema / properties / font / description
      Previous value: -"FIGlet font name (default 'standard')."New value: +"Lettering style."
    • addedInput schema / properties / font / enum
      Added value: +[
+  "standard",
+  "banner",
+  "big",
+  "block",
+  "bubble",
+  "digital",
+  "lean",
+  "mini",
+  "script",
+  "shadow",
+  "slant",
+  "small"
+]
    • addedInput schema / properties / font / x-show-when
      Added value: +{
+  "mode": [
+    "text"
+  ]
+}
    • changedInput schema / properties / mode / description
      Previous value: -"'text' (default) renders 'text' via figlet+'font'; 'image' converts 'file' at 'width' chars. Any other value 400s."New value: +"Turn words into a banner, or turn a picture into characters."
    • changedInput schema / properties / text / description
      Previous value: -"Text to render. REQUIRED when mode=text (the default). Truncated at 100 characters."New value: +"The words to render as a banner. Up to 100 characters."
    • addedInput schema / properties / text / x-show-when
      Added value: +{
+  "mode": [
+    "text"
+  ]
+}
    • changedInput schema / properties / width / description
      Previous value: -"Output width in characters, 40-200 (mode=image)."New value: +"How many characters wide the picture is drawn."
    • addedInput schema / properties / width / x-show-when
      Added value: +{
+  "mode": [
+    "image"
+  ]
+}
  3. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false), so the bar is lower. The description adds the default mode and gating rules, but says nothing about whether the result is returned inline or written to a file/attachment despite readOnlyHint=false, and no rate or size behavior beyond what the schema already states.

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?

A single compact line with the core action front-loaded, followed by the mode/parameter rules. Nothing is redundant, and the '[category: generate]' tag is standard metadata rather than filler.

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?

With five parameters, zero required fields, and no output schema, the description supplies the critical gating rules an agent needs to call it correctly. The one remaining gap is that it never states the form of the returned art (inline text vs. file), which matters given there is no output schema.

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 description coverage is 100%, so the baseline is 3. The description goes one step further by documenting the cross-parameter conditional requirements (which parameter each mode demands), which the per-field schema descriptions and x-show-when hints only imply.

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 pair ('Convert text or an image to ASCII art') and immediately enumerates the two operating modes, so the agent knows exactly what the tool produces. No sibling in the list overlaps this capability, and the two-mode framing makes the tool self-distinguishing.

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 clear conditional usage: mode 'text' (default) requires 'text', mode 'image' requires 'file'. That tells the agent which configuration to pick, but it names no alternatives or exclusions (e.g., when to prefer another generator or converter for the same input).

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

All John's Essentials toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources