Skip to main content
Glama

RTL PDF

Make an Arabic, Urdu or Persian PDF

make_pdf_arabic
Idempotent

Create a PDF from Arabic, Urdu or Persian text, or text that mixes them with English, with every letter correctly joined, lines running right to left, and numbers, dates, phone numbers and Latin words kept in order. Suited to PDFs, printable files, letters, notices, invoices, certificates, menus and handouts in Arabic, Urdu or Persian. The text is printed exactly as given; light Markdown is supported: '# ' headings, blank lines between paragraphs, '- ' bullets, '1. ' numbered lists, '| a | b |' tables (a '|---|' row marks a header) and bold. Returns a download link that works for 24 hours. It only lays out text: it does not write, translate or change wording, and it does not make images.

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

Input Schema

NameRequiredDescriptionDefault
fontNo'auto' picks Nastaliq for Urdu and Naskh otherwise. Cairo and Tajawal are modern sans styles.auto
textYesThe full text to print, in Arabic, Urdu or Persian (English may be mixed in). Light Markdown allowed.
bleedNoAdd 3 mm bleed and crop marks for professional printing.
paperNoPage size.A4
titleNoDocument title for the PDF metadata and file name. Defaults to the first heading.
justifyNoJustify paragraph lines.
archivalNoExport as PDF/A-2a with PDF/UA-1 (archival and accessible), falling back to PDF/A-2b.
languageNoLanguage of the text. 'auto' detects Urdu and Persian letters.auto
font_sizeNoText size in points, 7 to 28. Leave empty for the font's default.
page_numbersNoPrint page numbers when there is more than one page.

Output Schema

NameRequiredDescriptionDefault
fontYes
pagesYes
paperYes
titleYes
languageYes
warningsNo
standardsNoPDF standards applied, if any.
expires_atYesUTC time after which the link stops working.
download_urlYesLink to the PDF.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations, the description discloses the 24-hour download-link lifetime, that the text is printed exactly as given with a specific Markdown subset, and explicit non-capabilities (no writing, translation, or images). These are material behavioral facts an agent cannot derive from readOnlyHint/idempotentHint alone.

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?

The capability statement is front-loaded and each sentence carries distinct information (function, use cases, Markdown subset, return link, limits). The use-case list is slightly long and listy, but nothing is genuinely redundant.

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?

With an output schema, 100% parameter coverage and annotations covering safety/idempotency, the description is sufficient for correct invocation. The only notable gap is that it never mentions the font or language selection knobs or the archival option, though the schema documents all of them.

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 would be 3, but the description adds real meaning by enumerating the supported Markdown constructs ('# ', '- ', '1. ', '| a | b |' tables with a '|---|' header row, **bold**) and clarifying that mixed English is permitted in the text. Font and language enum behavior is left to the schema.

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 a specific verb and resource ("Create a PDF from Arabic, Urdu or Persian text") and immediately differentiates the scope: joined letters, right-to-left lines, preserved numbers and Latin words. This is clearly distinct from the sibling check_arabic_text, which does not generate documents.

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?

It gives concrete use cases (letters, notices, invoices, certificates, menus, handouts) and clear exclusions ("does not write, translate or change wording, and it does not make images"). It stops short of explicitly routing to the sibling tool for validation-only needs, so it is strong but not a full when/when-not/alternative map.

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