MCP-Dubai

uae_holidays

Read-onlyIdempotent

Retrieve UAE federal public holidays for a chosen Gregorian year, including provisional lunar dates and confirmation status for Eid, Hijri New Year, and Mawlid.

Instructions

List all UAE federal public holidays for a Gregorian year.

Lunar holidays (Eid al-Fitr, Eid al-Adha, Hijri New Year, Mawlid, Arafat Day) are returned with provisional: true until the relevant MOHRE and FAHR observance circulars are published. Every lunar record carries official_observance_announced; false identifies a religious- date candidate rather than a confirmed day off.

Input Schema

Name	Required	Description	Default
`year`	No	Gregorian year. Defaults to the current year in Asia/Dubai. Currently 2026 and 2027 are shipped (2027 lunar dates are astronomical expectations).

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv0.4.1Oct 22, 2026

addedInput schema / properties / year / anyOf

Added value: +[
+  {
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / year / default
```
Previous value: -2026New value: +null
```

changedInput schema / properties / year / description

Previous value: -"Gregorian year. Currently 2026 and 2027 are shipped\n(2027 lunar dates are astronomical expectations)."New value: +"Gregorian year. Defaults to the current year in Asia/Dubai.\nCurrently 2026 and 2027 are shipped (2027 lunar dates are\nastronomical expectations)."

removedInput schema / properties / year / type
```
Removed value: -"integer"
```

First observedv0.4.0Jul 11, 2026

TDQS

A3.7/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 behavior, but the description adds valuable data-quality context: lunar holidays are provisional until MOHRE/FAHR circulars are published, and official_observance_announced=false identifies a candidate rather than a confirmed day off. It does not cover rate limits or auth, but the provisional-status caveat is meaningful beyond the annotations.

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 purpose is front-loaded in the first sentence, and the second paragraph explains the non-obvious provisional-flag behavior. It is appropriately sized, though the lunar-holiday caveat could be tightened slightly.

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?

An output schema exists and annotations cover safety traits, so the description need not explain return values. It completes the picture by explaining the provisional and official_observance_announced semantics, which are essential for correct interpretation of lunar holiday records.

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 single parameter is fully documented in the schema, including the Asia/Dubai default and 2026/2027 coverage. The description adds no parameter syntax or constraints beyond what the schema already provides, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: 'List all UAE federal public holidays for a Gregorian year.' This clearly distinguishes the tool's scope from next-holiday or single-date tools, though it does not explicitly name sibling alternatives like uae_next_holiday or is_uae_holiday.

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

Usage Guidelines3/5

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

Usage is implied by 'for a Gregorian year,' but the description provides no explicit when-to-use guidance, no exclusions, and no routing to alternatives such as uae_next_holiday or is_uae_holiday.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server