John's Essentials

generate_ascii_art

ASCII Art Generator — Convert text or an image to ASCII art. Mode 'text' (the default) draws the words in 'text'; mode 'image' converts 'file'. With no text and a file attached, the file is converted in either mode. [category: generate]

Input Schema

TableJSON Schema

Name	Required	Description	Default
`file`	No	The picture to convert, up to 10 MB. Used when Mode is Image, and also when Text is left empty; with words in Text and Mode on Text, the picture is ignored.
`font`	No	Lettering style.	standard
`mode`	No	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.	text
`text`	No	The words to draw. Longer than 100 characters is trimmed.
`width`	No	How many characters wide the picture is.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 26, 2026
- addedInput schema / properties / text / x-ui
```
Added value: +{
+  "unset_label": "The picture is converted instead"
+}
```

Changed2 schema fields changedSep 24, 2026

changedInput schema / properties / file / description

Previous value: -"The picture to convert (max 10 MB)."New value: +"The picture to convert, up to 10 MB. Used when Mode is Image, and also when Text is left empty; with words in Text and Mode on Text, the picture is ignored."

removedInput schema / properties / file / x-show-when

Removed value: -{
-  "mode": [
-    "image"
-  ]
-}

Changed1 schema field changedSep 23, 2026
- addedInput schema / properties / width / x-ui
```
Added value: +{
+  "unit": "chars"
+}
```

Changed6 schema fields changedSep 11, 2026

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."

Changed8 schema fields changedSep 11, 2026

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"
+  ]
+}

First observedSep 5, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations only indicate readOnlyHint=false and destructiveHint=false, so the description carries the burden of explaining behavior. It adds mode-dependent logic and the automatic file fallback, going beyond the schema. It does not detail side effects or output format, but for a generator whose output is stated as ASCII art this is sufficient.

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?

The description is two dense sentences plus a category tag, with the core purpose front-loaded. Every clause adds information about modes or fallback behavior; there is no filler or repetition.

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?

The description covers the tool's central decision logic (text vs image mode, automatic file fallback), and the schema handles parameter constraints such as width bounds, font enum, file size, and truncation. Since there is no output schema, the output type is clear from 'ASCII art.' Minor gaps like font-only-in-text-mode are covered by schema x-show-when conditions.

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 100% with descriptive text for all five parameters, setting a baseline of 3. The description adds value by explaining the interplay between text, file, and mode—especially that an attached file is converted even when text mode is selected. This is meaningful beyond the individual field descriptions.

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 'Convert text or an image to ASCII art,' naming a specific verb and resource. It clearly distinguishes this tool from the many generate_* siblings by its domain (ASCII art) and by enumerating the two modes, 'text' and 'image'.

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?

The description explains when each mode applies ('Mode text (the default) draws the words in text; mode image converts file') and the fallback behavior ('With no text and a file attached, the file is converted in either mode'). This gives clear context of use, though it does not contrast this tool with an alternative sibling.

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 tools Inspect

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

Need Help?