Hotel Booking AI MCP

Check Room Availability

check_room_availability

Read-onlyIdempotent

Recheck the selected rate code, price, and inventory before booking.

Input Schema

TableJSON Schema

Name	Required	Description
`adults`	No	Number of adults in each room
`children`	No	Number of children in each room
`hotel_id`	Yes	TourMind hotel identifier
`user_key`	No	Optional TourMind user key for authenticated ToC access
`rate_code`	Yes	Rate code returned by query_room_rates
`room_count`	No	Number of rooms using the same occupancy
`check_in_date`	No	Check-in date in YYYY-MM-DD format
`children_ages`	No	Ages of the children in each room, each from 0 to 17
`check_out_date`	No	Check-out date in YYYY-MM-DD format

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 1, 2026

changedInput schema / properties / adults / description

Previous value: -"Number of adults per room"New value: +"Number of adults in each room"

addedInput schema / properties / children

Added value: +{
+  "description": "Number of children in each room",
+  "type": "integer"
+}

addedInput schema / properties / children_ages

Added value: +{
+  "description": "Ages of the children in each room, each from 0 to 17",
+  "items": {
+    "type": "integer"
+  },
+  "type": [
+    "null",
+    "array"
+  ]
+}

changedInput schema / properties / room_count / description

Previous value: -"Number of rooms"New value: +"Number of rooms using the same occupancy"

First observedAug 7, 2026

TDQS

A4.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is covered. The description adds modest behavioral context by framing the tool as a re-validation step, but does not describe any additional behavior such as how staleness is handled or what happens if the rate is no longer available.

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?

A single sentence that front-loads the action and context. There is no redundant material or repetition of schema field names.

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?

With a complete input schema, an output schema, and readOnly/idempotent/openWorld annotations, the one-sentence description is enough to place the tool in the booking workflow. Nothing necessary for correct invocation 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 the schema already document all 9 parametes. The description adds the useful hint that the rate_code is a 'selected' one, presumably from query_room_rates, but does not need to compensate for missing schema information.

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 description uses a specific verb ('recheck') and names the resources involved ('rate code, price, and inventory'). The phrase 'before booking' and 'selected' clearly distinguishes this from initial rate queries like query_room_rates or batch_query_room_rates.

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?

The description explicitly states when to use the tool: 'before booking'. It does not explicitly name alternatives or state when not to use it, but the 'recheck the selected...' wording makes the intended workflow position clear.

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

All Hotel Booking AI MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.