Skip to main content
Glama

Check an invoice for UAE e-invoicing readiness

check_einvoicing_readiness
Read-onlyIdempotent

Use this when the user asks whether an invoice has what UAE e-invoicing (PINT AE) needs, which fields are missing, or how to get their invoice data ready. A readiness check, not e-invoice validation: given an invoice's details, lists which PINT AE mandatory and conditional fields are present, missing or in the wrong format (seller and buyer legal name, TRN, company registration number from the trade licence or commercial registration, structured address with emirate code, country, invoice number, dates, currency and AED rate, unit codes, VAT category per line, totals that reconcile to the cent), with a plain-language fix for each. Only the accredited service provider validates the actual e-invoice. Use only details the user gave; leave out what they did not give rather than invent it, and the result will show it as missing. With a connected Fatura Go account, pass the invoice_id of a saved draft or invoice instead of the details to check that document. Do not use it for what a tax invoice must show under VAT law (tax_invoice_requirements) or for deadlines (einvoicing_timeline).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "check_einvoicing_readiness"
  }
}

Input Schema

NameRequiredDescriptionDefault
buyerNo
linesNo
sellerNo
totalsNoThe totals printed on the invoice, to check they reconcile.
currencyNoISO 4217, for example AED.
due_dateNoYYYY-MM-DD.
invoice_idNoConnected Fatura Go account only: the id of a saved draft or invoice to check, instead of passing its details.
issue_dateNoYYYY-MM-DD.
business_idNoConnected Fatura Go account only, with invoice_id.
paid_in_fullNotrue when nothing is due, so no due date is needed.
document_typeNoDefault: tax_invoice when the seller has a TRN, else commercial_invoice (out of scope of VAT).
invoice_numberNo
aed_exchange_rateNoWhen the currency is not AED.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare this is a safe, idempotent, closed-world read, so the description correctly spends its words elsewhere: it discloses the output shape (present / missing / wrong-format per mandatory and conditional PINT AE field, with a plain-language fix each), the data-handling rule ('use only details the user gave... the result will show it as missing' rather than inventing values), and the account-dependent branch (invoice_id/business_id for a saved draft). That is materially more than the annotations convey and prevents an agent from assuming validation authority or auto-filling gaps.

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 the trigger and the not-validation boundary, then the field list, then the data-honesty rule and the account path, then exclusions — a sensible order with no filler sentences. The long parenthetical field enumeration is dense but each item corresponds to a real check; it could be tightened into a shorter clause without losing information.

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?

There is no output schema, and the description compensates fully by describing the return content (per-field present/missing/malformed status plus a fix). For a 13-parameter nested tool it also covers the two operating modes (inline details vs saved invoice_id) and the omission-handling contract, so an agent knows both how to call it and what to expect back.

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 69% and nested, so the schema already documents much of the object tree; the description still adds domain meaning the schema cannot, by tying parameters to PINT AE obligations (which fields are mandatory vs conditional) and calling out specifics like the emirate code, country, AED rate, unit codes and reconciling totals. It also explains the invoice_id substitution and the 'don't invent missing values' rule, which changes how the agent should populate the nested seller/buyer/line objects. It stops short of explaining defaults or enum-driven branches such as document_type inference.

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 states a specific verb and resource ('check an invoice for UAE e-invoicing readiness') and immediately draws the boundary against a superficially similar capability: 'A readiness check, not e-invoice validation' and 'Only the accredited service provider validates the actual e-invoice.' It also enumerates the exact field families inspected (seller/buyer legal name, TRN, legal ID, emirate-coded address, VAT category per line, reconciling totals), which makes it unmistakable against siblings like check_trn or tax_invoice_requirements.

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

Usage Guidelines5/5

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

The opening sentence gives the triggering user intents verbatim ('whether an invoice has what UAE e-invoicing needs, which fields are missing, or how to get their invoice data ready'), and the closing sentence names explicit exclusions with the sibling to use instead: tax_invoice_requirements for VAT-law content and einvoicing_timeline for deadlines. It also gives the account-conditional alternative path (pass invoice_id instead of details) and points to list_accredited_service_providers' domain for actual validation.

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