Skip to main content
Glama

UAE tax invoice requirements

tax_invoice_requirements
Read-onlyIdempotent

Use this when the user asks what a UAE tax invoice must show, the difference between a full and a simplified tax invoice, or which kind a sale needs. Lists what a UAE tax invoice must show under Article 59 of the VAT Executive Regulation, for a full or a simplified tax invoice, with the clause for each item and when it must be issued. Give the customer's VAT status and the amount in AED (and reverse_charge if it applies) to get which kind the law allows; otherwise the full tax invoice is returned. The result states the law and, separately, Fatura Go's practice (a full tax invoice above AED 10,000); mention both when they differ. Do not use it to check one specific invoice for e-invoicing fields (check_einvoicing_readiness) or to make an invoice (create_draft_invoice).

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

Input Schema

NameRequiredDescriptionDefault
total_aedNoThe supply amount in AED, VAT included.
invoice_kindNoDefault auto: decided from the other fields.
reverse_chargeNo
buyer_vat_registeredNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description still adds real context beyond them: the fallback to a full tax invoice when buyer VAT status or amount is not supplied, and that the response carries the law and Fatura Go's practice (full invoice above AED 10,000) as separate statements that should both be surfaced when they diverge.

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 question, then behavior, inputs, output shape and exclusions in a tight sequence with no filler. It is a dense single paragraph, so the exclusions and the law-vs-practice note are harder to scan than they would be as separate sentences, but every sentence carries content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Since there is no output schema, the description carries the burden of describing the return, and it does reasonably well by naming the per-item clause and issue timing plus the law/practice split. However, it does not define the structure the result takes or how the two streams (regulation vs Fatura Go practice) are presented, which leaves the agent guessing at response shape for a fairly complex reference tool.

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 only 50% (reverse_charge and buyer_vat_registered have no schema descriptions), so the description must compensate, and it does: it explains that customer VAT status plus the AED amount drive which invoice kind the law allows, and that reverse_charge matters 'if it applies'. It also states the default outcome (full invoice) when those inputs are absent, though it does not explain the 'auto' enum values in any depth.

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 and resource ('Lists what a UAE tax invoice must show under Article 59'), scopes it to full vs simplified invoices, and names the clause plus issue timing. It also names the two siblings it is not, so an agent can separate it from check_einvoicing_readiness and create_draft_invoice without opening any schema.

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?

Opens with the exact user questions that select this tool (what a tax invoice must show, full vs simplified, which kind a sale needs) and closes with explicit exclusions routed to named alternatives. Both the when and the when-not are stated, not implied.

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