Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

conversion_braille

Read-onlyIdempotent

Convert text to and from Grade 1 or 2 Unicode Braille. Encode plain text into braille or decode braille back to Latin text for preview and education.

Instructions

Braille Converter (Grade 1 & 2). Convert text to and from Unicode Braille patterns (U+2800-U+28FF), in either uncontracted Grade 1 (letter-by-letter) or contracted Grade 2 (word/letter-group contractions). Use it to preview how labels, signage, or short copy render in braille cells, or to read back braille into Latin text; it is a preview/education aid, not a certified textbook/Nemeth/music transcription engine. Runs locally on the supplied text: read-only, non-destructive, contacts no external service, and is rate-limited. Returns the braille (or decoded text) string, the ASCII-braille form, per-conversion analysis stats, and reference braille_info for the chosen grade.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesInput to convert: plain text when operation=encode, or a Unicode braille string when operation=decode. Trimmed; must be non-empty. Unsupported characters become the question-mark braille cell.
operationYesencode = text to braille; decode = braille to text.
gradeNo1 = uncontracted (each letter individually); 2 = contracted (uses word/letter-group contractions, ~20-30% shorter).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successNoWhether the conversion succeeded.
resultNoThe converted output: braille for encode, Latin text for decode.
analysisNoPer-conversion stats (operation, input_length, output_length, compression_ratio, character_stats, braille_stats); null on error.
braille_infoNoReference facts for the selected grade (name, description, cell_structure, inventor, supported_chars, etc.).
gradeNoThe braille grade used.
ascii_brailleNoASCII-braille (computer braille) form of the braille output.
errorNoError message, present only when success is false.
Behavior5/5

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

Annotations provide readOnlyHint, destructiveHint, idempotentHint, and openWorldHint. The description adds value by stating it runs locally, is read-only, non-destructive, contacts no external service, is rate-limited, and details return values (braille string, ASCII-braille, stats, reference). No contradiction with annotations.

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 a single paragraph with no redundant information. It front-loads the core purpose and then adds necessary details about usage, behavior, and output. Every sentence is meaningful and efficient.

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

Completeness5/5

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

Given the tool's complexity (two grades, encode/decode, output structure) and the existence of an output schema, the description fully explains what the tool does, its limitations (not certified), behavior (local, rate-limited), and return value structure. No gaps remain.

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 100%, so the schema already documents all three parameters (text, operation, grade) with descriptions and examples. The description does not add additional parameter-level detail but provides context for the overall function. Baseline 3 is appropriate.

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 clearly states it is a Braille Converter for Grade 1 & 2, converting between text and Unicode Braille patterns. It differentiates from sibling converters by specifying grades and use cases (preview/education aid), making its purpose unambiguous.

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 explicitly states when to use: 'preview how labels, signage, or short copy render in braille cells' and 'read back braille into Latin text.' It also clarifies it is not for certified transcriptions (textbook/Nemeth/music), providing clear context. It does not mention alternatives among siblings but is sufficiently precise.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Jambozx/onlinecybertools-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server