Skip to main content
Glama

UAE VAT return deadline

vat_filing_deadline
Read-onlyIdempotent

Use this when the user asks when a UAE VAT return is due or must be paid for a month or quarter, or what their next VAT deadline is from the period alone. The UAE VAT return filing and payment deadline for a tax period: 28 days after the period ends (the 28th of the following month), moved to the next working day for a weekend or UAE public holiday, with days left. Give one of period_end (a date), month (a monthly period) or quarter_ending (the last month of a quarter). With none, returns the current and next periods for period_type and quarter_group (default quarterly, March/June/September/December). Do not use it for a connected business's own VAT figures or unfiled periods (get_vat_summary, get_whats_due).

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

Input Schema

NameRequiredDescriptionDefault
monthNoYYYY-MM: a monthly tax period.
period_endNoYYYY-MM-DD: the last day of the tax period.
period_typeNo
quarter_groupNoThe months your quarters end in, as shown in EmaraTax.
quarter_endingNoYYYY-MM: the last month of a quarterly tax period.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description still adds substantive domain behavior beyond them: the 28-day rule, the shift to the next working day for weekends or UAE public holidays, the inclusion of 'days left', and the defaults applied when no period is supplied.

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 usage trigger is front-loaded, followed by the rule, the inputs, the default behavior, and the exclusions in a logical order. It is dense and slightly overloaded with parenthetical asides, but no sentence is filler.

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?

There is no output schema, and the description compensates by indicating what comes back: the deadline with days remaining, and current plus next periods when no period is given. For a five-parameter, zero-required lookup tool this is close to complete; only the exact response shape is left implicit.

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 80%, so the baseline would be 3, but the description adds genuine selection logic: 'Give one of period_end, month or quarter_ending' tells the agent these are mutually exclusive alternatives rather than additive filters. It also documents the no-parameter fallback and the default quarter_group (Mar/Jun/Sep/Dec), which the schema does not spell out.

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 ('when a UAE VAT return is due or must be paid') and states exactly what is computed: the filing/payment deadline for a tax period. It also names the sibling tools it must not be confused with (get_vat_summary, get_whats_due), so the agent can distinguish it without opening schemas.

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?

It gives explicit when-to-use triggers ('when the user asks when a UAE VAT return is due... or what their next VAT deadline is') and explicit exclusions ('Do not use it for a connected business's own VAT figures or unfiled periods'), pointing at the correct alternatives. Both the positive and negative routing conditions are present.

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