Skip to main content
Glama
sepehr071

otaghak-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Holidays and weekdays

ot_holidays
Read-onlyIdempotent

List Iranian public holidays, including Fridays, across a date range with Jalali dates and weekdays. Use to plan long weekends and spot dates that may have higher stay rates.

Instructions

List Iranian public holidays (Fridays included) in a date range, with Jalali dates and weekdays.

Holiday flags are filled only about 7 weeks ahead: later days show no holidays, which means unknown, not working days. Use to plan around long weekends; weekend nights (Wed, Thu) and holidays usually cost more (see ot_room_calendar).

Input Schema

NameRequiredDescriptionDefault
endYesLast day (inclusive), e.g. '2026-12-31'; max a year after start.
startYesFirst day YYYY-MM-DD, e.g. '2026-10-20'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.2.0
    • changedInput schema / properties / end / description
      Previous value: -"Last day (inclusive), e.g. '2026-12-31'. At most a year after start."New value: +"Last day (inclusive), e.g. '2026-12-31'; max a year after start."
    • removedInput schema / properties / end / title
      Removed value: -"End"
    • changedInput schema / properties / start / description
      Previous value: -"First day, Gregorian YYYY-MM-DD, e.g. '2026-10-20'."New value: +"First day YYYY-MM-DD, e.g. '2026-10-20'."
    • removedInput schema / properties / start / title
      Removed value: -"Start"
    • removedInput schema / title
      Removed value: -"ot_holidaysArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "ot_holidaysDictOutput",
-  "type": "object"
-}New value: +null
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds genuinely non-obvious behavior: holiday flags are only populated ~7 weeks ahead, and blank days mean 'unknown, not working days'. It also discloses the return content (Jalali dates, weekdays) with no output schema present.

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

Conciseness5/5

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

Three tight sentences, front-loaded with what the tool returns, then the critical data-freshness caveat, then the usage/pricing hook. No filler or repetition.

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 two-parameter read-only lookup with no output schema, the description supplies everything needed: what comes back, the reliability limit on the holiday flags, and where to go for the pricing consequence. Nothing an agent needs to call it correctly is missing.

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 description coverage is 100%, so both date parameters, their formats, and the one-year maximum span are already documented in the schema. The description adds no format or constraint detail beyond that, so the baseline 3 applies.

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?

States a specific verb and resource ('List Iranian public holidays') with scope ('in a date range') and output content ('with Jalali dates and weekdays'). It distinguishes itself from the sibling ot_room_calendar by cross-referencing it for pricing context rather than duplicating it.

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?

Explicitly says 'Use to plan around long weekends' and points to ot_room_calendar for the price implication of weekend nights and holidays. No explicit when-not-to-use or exclusion of other date tools, so it stops short of a 5.

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

Deploy Server

Other Tools