Skip to main content
Glama

RTL PDF

Check Arabic, Urdu or Persian text

check_arabic_text
Read-onlyIdempotent

Check Arabic, Urdu or Persian text for problems that break PDFs, search and copy-paste: pre-shaped glyph characters and reversed letter order (typical of text copied out of a broken PDF), Persian or Urdu letters mixed into Arabic and the reverse, hidden direction-control characters, mixed digit systems, and characters the fonts cannot print. Returns the issues in English and Arabic and, when a safe fix exists, a fixed version of the text for the user to review. Deterministic rules; no AI.

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

Input Schema

NameRequiredDescriptionDefault
textYesThe text to check.
languageNoLanguage of the text, or 'auto'.auto

Output Schema

NameRequiredDescriptionDefault
okYes
issuesYes
languageYes
fixed_textNoA corrected version of the text, when a safe fix exists.
suggested_fontNo
arabic_script_shareNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish that this is a read-only, idempotent, non-destructive, closed-world operation, so the description's added value is in what it discloses beyond that: deterministic rule-based checking with 'no AI', results reported in both English and Arabic, and a proposed fixed text returned only when a safe fix exists and only for the user to review. The non-destructive framing of the fix suggestion is useful behavioral context.

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?

Two sentences, front-loaded with the tool's purpose and defect list before the return-behavior note, with no filler or restated title. The first sentence is dense with a long enumeration but every clause carries diagnostic meaning.

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 checking tool with an output schema and full annotation coverage, the description is nearly complete: it covers what is checked, that findings come back bilingual, and that a reviewed fix may be included. Only the treatment of the language/auto parameter is left entirely to the schema.

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 coverage is 100%, so the schema already documents both parameters ('text' with length bounds, 'language' with enum and 'auto' default). The description adds no parameter-level detail such as what 'auto' detection does or how language choice affects the findings, so the baseline 3 applies.

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 gives a specific verb ('Check') plus the exact resource (Arabic, Urdu or Persian text) and enumerates the concrete defect classes it detects: pre-shaped glyphs, reversed order, mixed-script letters, direction-control characters, mixed digit systems, and unprintable characters. An agent can tell this is a text-diagnosis tool, not a PDF-generating tool like make_pdf_arabic.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: 'typical of text copied out of a broken PDF' signals the scenario where this tool is wanted, but there is no explicit when-to-use statement, no mention of prerequisites, and no routing to or away from the sibling make_pdf_arabic. The agent must infer applicability from the problem list.

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