Skip to main content
Glama

UAE e-invoicing timeline

einvoicing_timeline
Read-onlyIdempotent

Use this when the user asks when UAE e-invoicing starts, when they must appoint a service provider, whether e-invoicing applies to them, or the penalties. The UAE e-invoicing mandate: go-live and service-provider (ASP) deadlines for each group of businesses, days left, scope, exclusions and penalties, with official sources. Give who the business sells to, its annual revenue band and whether it is a government entity to get the dates that apply to it. Do not use it for the list of accredited providers (list_accredited_service_providers) or to check an invoice's fields (check_einvoicing_readiness).

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

Input Schema

NameRequiredDescriptionDefault
sells_toNo
annual_revenueNoAnnual revenue in AED.
government_entityNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds that results are sourced from official references and that dates are conditional on business attributes, which is useful, but 'with official sources' sits slightly awkwardly against openWorldHint=false and no explanation of freshness or citation format is given.

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 conditions, then the payload, then the input requirements, then the exclusions — a logical order with no filler. It is dense and runs long for a single description, but every clause carries routing or input 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?

With no output schema, the description carries the burden of describing returns and does so explicitly (deadlines, days remaining, scope, exclusions, penalties, sources). Combined with the input guidance and sibling routing, an agent has everything needed to call it correctly.

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 33% (only annual_revenue is documented), so the description must compensate, and it does: it tells the agent to supply who the business sells to, its annual revenue band and whether it is a government entity, and explains that these determine which dates apply. It does not restate the enum values or clarify the AED unit beyond the schema, keeping it at 4 rather than 5.

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 resource (UAE e-invoicing mandate) and enumerates exactly what it returns: go-live and ASP deadlines per business group, days left, scope, exclusions and penalties. It also names the sibling tools it is not, so an agent can separate it from list_accredited_service_providers and check_einvoicing_readiness 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 concrete trigger questions (when does it start, when to appoint a provider, does it apply, penalties) and closes with explicit exclusions routed to named alternatives. Both the when-to-use and when-not-to-use sides are covered.

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