uae-einvoice-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| lookup_business_trnA | Validate a UAE Tax Registration Number (15-digit TRN) or Tax Identification Number (10-digit TIN): format, UAE country prefix, Peppol AE:TIN check digit, and derived Peppol participant ID (0235:TIN). Does not call the live FTA register. |
| check_invoice_complianceA | Structural PINT AE / UAE e-invoicing checks (parties, tax IDs, totals arithmetic, tax breakdown, lines). Returns errors, warnings, a score, and derived Peppol IDs. Prefer check_pint_ae_fields for the full 51-field matrix. |
| check_pint_ae_fieldsA | Evaluate invoice JSON against the 51-field UAE e-invoice / PINT AE mandatory field matrix. Returns per-field present/missing/invalid/not_applicable status, completion %, and gaps. |
| generate_pint_ae_xmlA | Generate a UBL 2.1 PINT AE-shaped Invoice/CreditNote XML stub from invoice JSON. Runs the 51-field checklist first; with strict=true refuses to emit XML when mandatory applicable fields are incomplete. |
| get_einvoicing_requirementsA | Return the UAE e-invoicing mandate timeline, technical baseline (PINT AE / Peppol / ASP), and next actions for a business segment (large, sme, government, or all). Optional annual revenue (AED) auto-selects large vs SME. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Most tools target clearly distinct actions: TRN lookup, invoice validation, field-matrix checking, XML generation, and requirements lookup. The only potential confusion is between check_invoice_compliance and check_pint_ae_fields, but the descriptions explicitly differentiate structural checks from the full 51-field matrix.
Tool names follow a consistent lowercase snake_case verb_noun pattern: lookup_, check_, check_, generate_, get_. The only minor inconsistency is using both 'lookup' and 'get' for retrieval actions, but the overall pattern is predictable and readable.
Five tools is well-scoped for a UAE e-invoicing helper server. Each tool covers a distinct need without redundancy, and the count feels appropriate for the domain.
The server covers TRN validation, compliance checking, field-matrix evaluation, XML generation, and regulatory requirements lookup, which forms a coherent workflow. Minor gaps exist, such as no live FTA register lookup or explicit support for more advanced invoice operations, but the core e-invoicing lifecycle is reasonably complete.