Hotel Booking AI MCP

Query Room Rates

query_room_rates

Read-onlyIdempotent

Get live room types and rate products for a hotel and stay.

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
`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

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, and openWorld behavior, so the description only needs to add nuance. It adds 'live,' indicating real-time rates, but does not disclose details like response freshness or auth requirements. This is adequate but not rich.

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 front-loaded sentence with no filler. It conveys the core purpose immediately and leaves details to the schema.

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?

For a read-only query tool with a complete schema, output schema, and safety annotations, the description is nearly sufficient. It could have referenced batch_query_room_rates or clarified that stay dates are optional, but those gaps are minor.

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%, with every parameter explained inline. The description adds no parameter-level detail beyond what the schema already provides, 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?

The description uses a specific verb ('Get'), names the resource ('room types and rate products'), and scopes it ('for a hotel and stay'). This clearly distinguishes it from availability checks and booking creation, and the 'live' qualifier signals fresh data.

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

Usage Guidelines2/5

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

There is no guidance on when to prefer this tool over siblings such as batch_query_room_rates or check_room_availability. The description implies a single-hotel/stay query but never states exclusions or alternatives.

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.