Skip to main content
Glama

Fancy text for Discord, Twitch and bios

style_text
Read-onlyIdempotent

Convert plain text into Unicode "font" styles that paste anywhere fonts can't be changed: Discord and Twitch chat, usernames, bios, stream titles. Styles: bold (Bold), italic (Italic), bolditalic (Bold italic), sansbold (Sans bold), sansitalic (Sans italic), sansbolditalic (Sans bold italic), script (Script), boldscript (Bold script), fraktur (Gothic), boldfraktur (Bold gothic), double (Double-struck), mono (Monospace), smallcaps (Small caps), superscript (Tiny (superscript)), wide (Wide (aesthetic)), circled (Bubbles), negcircled (Dark bubbles), squared (Squares), negsquared (Dark squares), strike (Strikethrough), underline (Underline), slash (Slashed), upside (Upside down). Leave "style" empty to get every style at once. Screen readers read these characters poorly, so suggest plain text for important information.

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

Input Schema

NameRequiredDescriptionDefault
textYesText to convert.
styleNoOptional single style.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds real context on top: the output survives anywhere fonts can't be changed, omitting 'style' returns every style at once, and there is an accessibility tradeoff. It stops short of describing the return shape (a single string versus a mapping of styles), which matters given no output schema.

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: purpose and target surfaces come first, the accessibility warning last. The long inline enumeration of 23 styles largely repeats the schema enum, but each entry adds a display label, so the length is defensible rather than padding.

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 two-parameter conversion tool with full schema coverage and annotations, the description covers purpose, contexts, the empty-style case, and a caveat. The remaining gap is output format — especially what 'every style at once' returns — which cannot be inferred since no output schema exists.

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%, so the baseline is 3, but the description earns more by mapping raw enum values to human-readable labels ('fraktur (Gothic)', 'superscript (Tiny (superscript))', 'circled (Bubbles)') and by explaining what happens when 'style' is omitted — neither of which the schema states.

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 ('Convert plain text into Unicode "font" styles') and immediately names the concrete scopes it serves (Discord/Twitch chat, usernames, bios, stream titles). No sibling tool in the list does text styling, so the distinction is unambiguous from the first sentence alone.

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

Usage Guidelines5/5

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

Gives explicit when-to-use contexts (chat, usernames, bios, stream titles) and an explicit when-not in the form of the accessibility caveat: 'Screen readers read these characters poorly, so suggest plain text for important information.' It also explains the empty-style fallback, so the agent knows both selection paths.

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