Skip to main content
Glama

Bindler: UAE Corporate Tax, CSRD scope, EU AI Act, CBAM and statutory deadlines

compliance_deadlines

Read-onlyIdempotent

Returns the statutory dates for a regime with the Article behind each one, and for UAE Corporate Tax computes the actual due date from the financial year end. Use it when someone asks: when is my UAE corporate tax return due, what is the deadline for a financial year ending 31 March or 31 December, when do I have to pay the corporate tax, how many days have I got left, is the deadline 30 September 2026, what is the penalty for filing late, when is the first CBAM declaration due, when does the CBAM definitive period start, when do CBAM certificates go on sale, is there still a quarterly CBAM report. Use this rather than recalling a date: UAE Corporate Tax has no fixed annual deadline, it is nine months after each company's own Tax Period end, and the CBAM dates were rewritten by Regulation (EU) 2025/2083.

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": {
      "regime": "<regime>"
    },
    "name": "compliance_deadlines"
  }
}

Input Schema

NameRequiredDescriptionDefault
regimeYesOne of: uae_ct | cbam
financial_year_endNoFor uae_ct, the Tax Period end as YYYY-MM-DD. The due date is computed from it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, closed-world behavior, so the bar is lower, and the description still adds real domain context: UAE CT deadlines are derived per company, and CBAM dates were rewritten by Regulation (EU) 2025/2083. It does not describe the response shape or whether Article citations are always present.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The lead sentence is well front-loaded and the two explanatory clauses at the end earn their place. The middle stretch is a long chain of near-duplicate question phrasings ('what is the deadline for a financial year ending 31 March or 31 December', 'is the deadline 30 September 2026') that helps retrieval but reads as padding.

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, yet the description notes that each date comes with its governing Article, which is the key return-value fact. For a two-parameter lookup tool with full annotation coverage, the remaining omission is only the exact response structure.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the schema already states that financial_year_end drives the computed due date for uae_ct. The description reinforces the nine-months-after-Tax-Period-end rule but adds no syntax, format or edge-case guidance beyond the schema.

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 first sentence states the verb, the resource and the two regimes precisely: statutory dates with the Article behind each, and a computed due date for UAE Corporate Tax. An agent can distinguish it from uae_corporate_tax or cbam_cost purely from this text.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit trigger list ('use it when someone asks: when is my UAE corporate tax return due...') and a clear directive to prefer it over recalling a date. It stops short of naming a sibling tool as the wrong choice, so routing versus uae_corporate_tax or cbam_cost is left implicit.

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