Skip to main content
Glama
sepehr071

otaghak-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Room calendar

ot_room_calendar
Read-onlyIdempotent

Check a room's day-by-day calendar for nightly prices, discounts, free or booked status, stay-length limits, and booking rules. Use it to find free dates, cheap nights, or allowed stays.

Instructions

Get a room's calendar day by day: nightly price after and before discount (Toman), free or booked, instant booking, min and max nights when arriving that day, weekend, public holiday, late checkout.

A night is priced on its arrival day. Absent keys: price_before_discount = no discount, instant / weekend / holiday / late_checkout = no. Use to find free dates, cheap nights or allowed stay lengths. Next: ot_price_quote for a stay.

Input Schema

NameRequiredDescriptionDefault
endNoLast day (inclusive), e.g. '2026-11-20'. Default: start + 30 days.
startNoFirst day YYYY-MM-DD, e.g. '2026-10-20'. Default: today.
room_idYesRoom id (code), e.g. 2512254.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv0.2.0
    • changedInput schema / properties / end / description
      Previous value: -"Last day (inclusive), e.g. '2026-11-20'. Default: 30 days after start. Days past the open calendar (end of next Jalali month) are not returned."New value: +"Last day (inclusive), e.g. '2026-11-20'. Default: start + 30 days."
    • removedInput schema / properties / end / title
      Removed value: -"End"
    • removedInput schema / properties / room_id / title
      Removed value: -"Room Id"
    • changedInput schema / properties / start / description
      Previous value: -"First day, Gregorian YYYY-MM-DD, e.g. '2026-10-20'. Default: today."New value: +"First day YYYY-MM-DD, e.g. '2026-10-20'. Default: today."
    • removedInput schema / properties / start / title
      Removed value: -"Start"
    • removedInput schema / title
      Removed value: -"ot_room_calendarArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "ot_room_calendarDictOutput",
-  "type": "object"
-}New value: +null
  2. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so the safety profile is covered. The description adds real behavioral semantics beyond them: pricing is anchored to the arrival day, and absent keys have defined defaults (no discount, instant/weekend/holiday/late_checkout = no), which is exactly the kind of context an agent needs to interpret the response.

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-loads the core purpose and then compresses the return fields into a dense list; each clause (absent-key defaults, next step) carries information. The telegraphic style is slightly terse but not padded, so every sentence earns its place.

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?

With no output schema, the description does the work of describing the return payload field by field and explains how missing keys should be read, which is essential for a calendar-dump tool. Coverage is strong, though the encoding of 'free or booked' and the min/max nights fields could be spelled out a bit more.

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 start/end/room_id defaults are already documented in the schema, establishing a baseline of 3. The description's 'A night is priced on its arrival day' helps interpret the day-keyed response, but adds no syntax or format detail for the individual parameters themselves.

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+resource+granularity ('Get a room's calendar day by day') and enumerates exactly what each day contains (price before/after discount, free/booked, instant booking, min/max nights, weekend, holiday, late checkout). This is clearly distinguishable from siblings like ot_room or ot_price_quote, which are routed to explicitly.

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?

Gives concrete use cases ('find free dates, cheap nights or allowed stay lengths') and names the natural follow-up tool ('Next: ot_price_quote for a stay'), which routes the agent well. It does not state when NOT to use this tool or contrast it with ot_room, so it stops short of explicit exclusion guidance.

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