Skip to main content
Glama

Convert text to Latin ASCII or make a URL slug

text_transliterate
Read-only

Transliterate text to Latin ASCII, or make a URL slug from it. Covers Cyrillic, Greek, Turkish, German, Nordic, Polish, Vietnamese and accented Latin letters. Characters with no table entry (Arabic, Hebrew, CJK ...) are kept and listed in unconverted, not guessed. Up to 2,000 characters. Pure code. Related tools on this server, for a different need: text_answer when you need answers a question from the given text only; text_chunk when you need to generate overlapping text chunks with character offsets. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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

Input Schema

NameRequiredDescriptionDefault
modeNoascii (default) or slug (lowercase words joined by the separator)
textYesThe text, up to 2,000 characters
separatorNoSeparator for slugs: - (default), _ or .

Output Schema

NameRequiredDescriptionDefault
modeNo
inputNo
resultNo
sourceNo
checkedAtNo
unconvertedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only say readOnlyHint/openWorldHint; the description adds real behavior: characters without a table entry are kept and reported in 'unconverted' rather than guessed, 'Pure code' signals a deterministic non-LLM transform, and the 2,000-character cap plus billing model ('$0.002 per successful call', failures not charged) are disclosed. Those are exactly the traits annotations cannot convey.

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 purpose and script coverage, with limits, behavior, sibling routing, and pricing in descending order of importance. The 'Related tools on this server, for a different need' clause and the multi-network pricing detail are somewhat padded for a transliteration tool, but nothing is genuinely redundant.

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?

An output schema exists, so return values need not be spelled out, yet the description still explains the 'unconverted' field and the no-guessing policy. Modes, limits, determinism, and cost are all covered, leaving no ambiguity for a three-parameter transform tool.

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%, and the schema already defines ascii/slug modes, the 2,000-character limit, and the separator options, so the baseline is 3. The description reinforces 'URL slug' and the lowercase-words-joined-by-separator behavior but adds no syntax or default detail the schema lacks.

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 (transliterate) and resource (text), plus its second mode (URL slug) in the first sentence. The script coverage list (Cyrillic, Greek, Turkish, German, Nordic, Polish, Vietnamese, accented Latin) makes the scope unmistakable and separates it from any sibling.

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?

Explicitly names alternatives (text_answer, text_chunk) with the condition that selects each, prefaced by 'for a different need', which tells the agent this tool is not the one for Q&A or chunking. It does not state any when-not condition for the transliteration itself (e.g., what to do for Arabic/CJK input), which keeps it short of a 5.

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