Skip to main content
Glama
sepehr071

otaghak-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Late checkout

ot_late_checkout
Read-onlyIdempotent

Check if a room offers late checkout, how many hours, the price in Toman, and whether it can be booked on a specified departure date.

Instructions

Check whether a room offers late checkout, for how many hours and at what price (Toman, a unit not confirmed on the site), and with check_out whether it can be booked on that departure day (offered rooms are often closed for it on a given day).

Use when the user wants to leave later than the check-out time. ot_price_quote adds it to a total with late_checkout_hours.

Input Schema

NameRequiredDescriptionDefault
room_idYesRoom id (code), e.g. 2512254.
check_outNoDeparture day to check, e.g. '2026-10-23'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.2.0
    • changedInput schema / properties / check_out / description
      Previous value: -"Departure day to check, Gregorian YYYY-MM-DD, e.g. '2026-10-23'."New value: +"Departure day to check, e.g. '2026-10-23'."
    • removedInput schema / properties / check_out / title
      Removed value: -"Check Out"
    • removedInput schema / properties / room_id / title
      Removed value: -"Room Id"
    • removedInput schema / title
      Removed value: -"ot_late_checkoutArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "ot_late_checkoutDictOutput",
-  "type": "object"
-}New value: +null
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the bar is lower; the description still adds real behavioral context: the price unit is Toman and explicitly flagged as unverified, and it warns that offered rooms are often closed for late checkout on a given day. That quirk is genuinely useful and not derivable from structured fields.

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 core purpose, then usage. The second sentence is a bit clause-heavy ('with check_out whether it can be booked on that departure day') but every element carries information and nothing is redundant 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?

With no output schema, the description does the work of describing the return surface (offered or not, hours, price, bookability), which is what an agent needs. Minor gaps remain, such as how an 'unavailable' result is signaled, but it is nearly complete for a 2-parameter read tool.

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 description coverage is 100%, so the baseline is 3. The description goes beyond the schema by explaining what check_out actually does behaviorally (determines whether late checkout can be booked on that departure day) rather than merely restating 'departure day to check'.

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 (check whether a room offers late checkout) and enumerates the exact facets returned: availability, number of hours, price, and bookability on a given departure day. This is clearly distinguished from siblings like ot_price_quote, which it explicitly frames as a complementary tool.

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?

Gives an explicit triggering condition ('Use when the user wants to leave later than the check-out time') and names the related tool plus the parameter that connects them ('ot_price_quote adds it to a total with late_checkout_hours'). An agent knows both when to call this and how it chains.

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