Skip to main content
Glama

Check UAE VAT registration

check_vat_registration
Read-onlyIdempotent

Use this when the user asks whether they must or may register for UAE VAT, about the AED 375,000 or 187,500 thresholds, or by when they must register. Says whether a UAE business must register for VAT (taxable supplies and imports over AED 375,000 in the past 12 months, or expected to go over it in the next 30 days), may register voluntarily (supplies or taxable expenses over AED 187,500) or does not need to yet, with both tests shown. When registration is mandatory it gives the 30-day registration deadline; pass required_since (the day the threshold was crossed) to get the date and days left. Amounts are in AED; taxable supplies include standard- and zero-rated supplies and imports, not exempt ones. Do not use it for corporate tax registration (ct_registration_deadline).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "taxable_supplies_last_12_months": "<taxable_supplies_last_12_months>"
    },
    "name": "check_vat_registration"
  }
}

Input Schema

NameRequiredDescriptionDefault
uae_residentNoDefault true. Non-residents making taxable supplies in the UAE must register at any amount.
required_sinceNoYYYY-MM-DD: the day the AED 375,000 threshold was crossed (or first expected to be), for the 30-day deadline.
taxable_expenses_last_12_monthsNoTaxable expenses over the past 12 months, AED (voluntary test).
taxable_supplies_last_12_monthsYesTaxable supplies and imports over the past 12 months, AED.
expected_taxable_supplies_next_30_daysNoTaxable supplies and imports expected in the next 30 days alone, AED.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so safety is covered; the description goes further by describing the output verdict shape ('with both tests shown'), the 30-day deadline behavior, and the causal link that passing required_since yields the date and days left. It omits only edge-case behavior such as how non-residents are handled (that is left to the schema).

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 verdict set, then thresholds, then parameters, then exclusion — a logical order with no filler sentences. It is dense and long for a single paragraph, but nearly every clause carries decision-relevant 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?

For a five-parameter calculation tool with no output schema, the description supplies what is otherwise missing: the return semantics (verdict plus both tests), the conditional deadline output, threshold values, and the boundary against the corporate tax tool. Nothing an agent needs to call it correctly appears absent.

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 100%, so baseline is 3, but the description adds genuine meaning: it defines the scope of 'taxable supplies' (standard- and zero-rated supplies and imports, not exempt), clarifies currency, and explains that required_since should be the day the threshold was crossed because it drives the deadline output.

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?

Names a specific verb and resource ('Says whether a UAE business must register for VAT') and enumerates the three possible verdicts (must, may voluntarily, does not need to yet). It also explicitly separates itself from the corporate tax sibling, so an agent can discriminate without opening either 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 triggering user question, lists the concrete thresholds (AED 375,000 / 187,500) that route to this tool, and closes with an explicit exclusion: 'Do not use it for corporate tax registration (ct_registration_deadline).' Both when-to-use and when-not-to-use are stated.

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