Skip to main content
Glama

UAE corporate tax registration deadline

ct_registration_deadline
Read-onlyIdempotent

Use this when the user asks by when a company, free zone company or individual must register for UAE corporate tax, or about the late-registration penalty. The UAE corporate tax registration deadline under FTA Decision No. 3 of 2024 for a resident company, free zone company or natural person with a business, with days left, the late-registration penalty and its official source. A company incorporated on or after 1 March 2024 has three months from incorporation; one incorporated earlier has a fixed date set by the month its licence was issued; a natural person registers by 31 March after the first calendar year with business turnover over AED 1,000,000. Use only dates the user gave; if a needed date is missing, the result says which one. Do not use it for VAT registration (check_vat_registration).

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": {
      "legal_form": "<legal_form>"
    },
    "name": "ct_registration_deadline"
  }
}

Input Schema

NameRequiredDescriptionDefault
legal_formYescompany (mainland), free_zone_company, or natural_person with a business.
incorporation_dateNoYYYY-MM-DD, if different from the licence date.
licence_issue_dateNoYYYY-MM-DD: the earliest trade licence.
turnover_over_1m_yearNoNatural person only: the first calendar year business turnover went over AED 1,000,000.
incorporated_before_1_march_2024NoUse when the exact incorporation date is not known.

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 declare this a read-only, idempotent, closed-world lookup, so the safety profile is covered. The description goes beyond that by disclosing the computation rules applied (three months from incorporation for post-1 March 2024 entities; fixed date keyed to licence-issue month otherwise; 31 March for natural persons) and the failure behavior of naming the missing input. It stops short of describing the full response shape, which is the only real gap.

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 usage trigger, then the substantive rules, then the exclusion — a sensible order. Slightly verbose, with some restatement of the title and decision number, but every sentence carries decision-relevant content rather than 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?

For a five-parameter calculator with no output schema, the description supplies the branching logic, the entity coverage, the exclusion, and the missing-input behavior. Return values are not spelled out beyond 'days left, penalty and official source', which leaves minor ambiguity about the response shape, but nothing needed to call it correctly is 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 the schema already defines each field, making 3 the baseline. The description adds business meaning the schema cannot: which rule each date feeds into, why an earlier incorporated entity falls back to a fixed date, and the natural-person turnover threshold that motivates turnover_over_1m_year.

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 resource and computed output: the UAE corporate tax registration deadline, days left, and the late-registration penalty, grounded in FTA Decision No. 3 of 2024. It also enumerates the covered entities (resident company, free zone company, natural person with a business), so an agent can tell this apart from VAT-related siblings at a glance.

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 an explicit trigger ('when the user asks by when a company ... must register ... or about the late-registration penalty') and closes with an explicit exclusion plus the correct alternative ('Do not use it for VAT registration (check_vat_registration)'). It also adds a data-hygiene rule: use only dates the user gave, and the result identifies any missing date.

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