1stay

Book Hotel

book_hotel

Idempotent

Book exactly one hotel room. The first 1Stay release does not support multi-room searches or reservations. Returns a secure checkout URL. This tool accepts no guest identity or payment fields. Name, email, phone, and payment details are collected on the secure checkout page.

Guest pays the hotel directly. Their credit card statement shows the hotel name, not 1Stay. Hotel's own confirmation number. Loyalty points apply automatically. The displayed total includes taxes and any applicable, itemized 1Stay Booking Fee.

Requires a rate_code from get_hotel_details, valid approximately 15 minutes. Expired codes are rejected.

Input Schema

TableJSON Schema

Name	Required	Description
`guests`	Yes	Number of guests, 1-10
`check_in`	Yes	Check-in date in YYYY-MM-DD format (e.g. 2026-05-06)
`hotel_id`	Yes	Hotel ID from search or details
`check_out`	Yes	Check-out date in YYYY-MM-DD format (e.g. 2026-05-07)
`rate_code`	Yes	Valid, unexpired rate code for the selected hotel, dates, and room
`external_reference_id`	No	Caller-defined unique reference ID for idempotency and retrieval

Output Schema

TableJSON Schema

Name	Required	Description	Default
`taxes`	No
`nights`	No
`status`	Yes
`message`	Yes
`check_in`	No
`currency`	No
`subtotal`	No
`check_out`	No
`rate_plan`	No
`room_type`	No
`hotel_name`	No
`booking_fee`	No
`booking_type`	No
`checkout_url`	No
`idempotency_hit`	No
`avg_nightly_rate`	No
`total_with_taxes`	No
`expires_in_minutes`	No
`cancellation_policy`	No
`confirmation_number`	No
`booking_fee_currency`	No
`external_reference_id`	No
`reward_points_eligible`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 24, 2026
- changedInput schema / properties / guests / description
```
Previous value: -"Number of guests"New value: +"Number of guests, 1-10"
```
- changedInput schema / properties / guests / maximum
```
Previous value: -9007199254740991New value: +10
```
- changedInput schema / properties / guests / minimum
```
Previous value: --9007199254740991New value: +1
```

Changed12 schema fields changedSep 19, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

removedInput schema / additionalProperties
```
Removed value: -false
```

changedInput schema / properties / check_in / description

Previous value: -"Check-in date in YYYY-MM-DD format (e.g. 2026-05-06), no more than 340 days from today"New value: +"Check-in date in YYYY-MM-DD format (e.g. 2026-05-06)"

addedInput schema / properties / guests / maximum
```
Added value: +9007199254740991
```
addedInput schema / properties / guests / minimum
```
Added value: +-9007199254740991
```

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedOutput schema / properties / expires_in_minutes / maximum
```
Added value: +9007199254740991
```
addedOutput schema / properties / expires_in_minutes / minimum
```
Added value: +-9007199254740991
```

addedOutput schema / properties / external_reference_id / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / external_reference_id / type
```
Removed value: -[
-  "string",
-  "null"
-]
```
addedOutput schema / properties / nights / maximum
```
Added value: +9007199254740991
```
addedOutput schema / properties / nights / minimum
```
Added value: +-9007199254740991
```

Changed11 schema fields changedAug 25, 2026

changedInput schema / $schema

Previous value: -"https://json-schema.org/draft/2020-12/schema"New value: +"http://json-schema.org/draft-07/schema#"

addedInput schema / additionalProperties
```
Added value: +false
```
removedInput schema / properties / guests / maximum
```
Removed value: -9007199254740991
```
removedInput schema / properties / guests / minimum
```
Removed value: --9007199254740991
```

changedOutput schema / $schema

Previous value: -"https://json-schema.org/draft/2020-12/schema"New value: +"http://json-schema.org/draft-07/schema#"

removedOutput schema / properties / expires_in_minutes / maximum
```
Removed value: -9007199254740991
```
removedOutput schema / properties / expires_in_minutes / minimum
```
Removed value: --9007199254740991
```

removedOutput schema / properties / external_reference_id / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / external_reference_id / type
```
Added value: +[
+  "string",
+  "null"
+]
```
removedOutput schema / properties / nights / maximum
```
Removed value: -9007199254740991
```
removedOutput schema / properties / nights / minimum
```
Removed value: --9007199254740991
```

Changed11 schema fields changedAug 24, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

removedInput schema / additionalProperties
```
Removed value: -false
```
addedInput schema / properties / guests / maximum
```
Added value: +9007199254740991
```
addedInput schema / properties / guests / minimum
```
Added value: +-9007199254740991
```

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedOutput schema / properties / expires_in_minutes / maximum
```
Added value: +9007199254740991
```
addedOutput schema / properties / expires_in_minutes / minimum
```
Added value: +-9007199254740991
```

addedOutput schema / properties / external_reference_id / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / external_reference_id / type
```
Removed value: -[
-  "string",
-  "null"
-]
```
addedOutput schema / properties / nights / maximum
```
Added value: +9007199254740991
```
addedOutput schema / properties / nights / minimum
```
Added value: +-9007199254740991
```

Changed1 schema field changedAug 19, 2026

changedInput schema / properties / check_in / description

Previous value: -"Check-in date in YYYY-MM-DD format (e.g. 2026-05-06)"New value: +"Check-in date in YYYY-MM-DD format (e.g. 2026-05-06), no more than 340 days from today"

Changed2 schema fields changedAug 18, 2026
- removedOutput schema / properties / booking_id
```
Removed value: -{
-  "type": "string"
-}
```
- addedOutput schema / properties / confirmation_number
```
Added value: +{
+  "type": "string"
+}
```

Changed3 schema fields changedAug 17, 2026

changedInput schema / properties / external_reference_id / description

Previous value: -"Your unique reference ID for this booking (for idempotency and retrieval)"New value: +"Caller-defined unique reference ID for idempotency and retrieval"

changedInput schema / properties / rate_code / description

Previous value: -"Rate code from get_hotel_details — you MUST call get_hotel_details first to get a valid rate_code before booking"New value: +"Valid, unexpired rate code for the selected hotel, dates, and room"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "avg_nightly_rate": {
+      "type": "number"
+    },
+    "booking_fee": {
+      "type": "number"
+    },
+    "booking_fee_currency": {
+      "type": "string"
+    },
+    "booking_id": {
+      "type": "string"
+    },
+    "booking_type": {
+      "type": "string"
+    },
+    "cancellation_policy": {
+      "type": "string"
+    },
+    "check_in": {
+      "type": "string"
+    },
+    "check_out": {
+      "type": "string"
+    },
+    "checkout_url": {
+      "type": "string"
+    },
+    "currency": {
+      "type": "string"
+    },
+    "expires_in_minutes": {
+      "type": "integer"
+    },
+    "external_reference_id": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "hotel_name": {
+      "type": "string"
+    },
+    "idempotency_hit": {
+      "type": "boolean"
+    },
+    "message": {
+      "type": "string"
+    },
+    "nights": {
+      "type": "integer"
+    },
+    "rate_plan": {
+      "type": "string"
+    },
+    "reward_points_eligible": {
+      "type": "boolean"
+    },
+    "room_type": {
+      "type": "string"
+    },
+    "status": {
+      "enum": [
+        "ACTION_REQUIRED",
+        "ALREADY_CONFIRMED"
+      ],
+      "type": "string"
+    },
+    "subtotal": {
+      "type": "number"
+    },
+    "taxes": {
+      "type": "number"
+    },
+    "total_with_taxes": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "status",
+    "message"
+  ],
+  "type": "object"
+}

Changed3 schema fields changedAug 10, 2026

removedInput schema / properties / guest_email

Removed value: -{
-  "description": "Guest email for confirmation",
-  "type": "string"
-}

removedInput schema / properties / guest_name

Removed value: -{
-  "description": "Guest full name",
-  "type": "string"
-}

changedInput schema / required

Previous value: -[
-  "hotel_id",
-  "rate_code",
-  "check_in",
-  "check_out",
-  "guests",
-  "guest_name",
-  "guest_email"
-]New value: +[
+  "hotel_id",
+  "rate_code",
+  "check_in",
+  "check_out",
+  "guests"
+]

Changed2 schema fields changedMar 25, 2026

changedInput schema / properties / check_in / description

Previous value: -"Check-in date (YYYY-MM-DD)"New value: +"Check-in date in YYYY-MM-DD format (e.g. 2026-05-06)"

changedInput schema / properties / check_out / description

Previous value: -"Check-out date (YYYY-MM-DD)"New value: +"Check-out date in YYYY-MM-DD format (e.g. 2026-05-07)"

First observedMar 18, 2026

TDQS

A4.6/5.0

Behavior5/5

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

The description goes well beyond the annotations by explaining that no guest identity or payment fields are accepted, that payment is collected on a secure checkout page, that the guest pays the hotel directly, and that the total includes taxes and any itemized booking fee. It also discloses rate-code expiry behavior holistically and confirms the hotel's own confirmation number is used.

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?

The description is organized into three short paragraphs with the core purpose and primary limitation front-loaded. Every sentence adds a distinct operational fact, and while some fragments are terse, none are filler or redundant.

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 booking tool with six parameters, an output schema, and a complex payment flow, the description covers all essential behavioral and operational aspects: what to pass, what happens after booking, what the user sees on the statement, and what prerequisites apply. The output schema can handle return-value details, and sibling tools like cancel_booking and get_booking cover downstream workflows.

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?

Since schema coverage is 100%, the schema already documents each parameter's meaning. The description adds valuable context for rate_code by explaining where it comes from, that it is valid only about 15 minutes, and that expired codes are rejected, which is not fully captured in the schema.

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 states a specific action and resource: 'Book exactly one hotel room.' It also differentiates the tool from siblings by noting the first release does not support multi-room searches/reservations, making it clear this is the reservation-creation tool and not search_hotels, get_hotel_details, or cancel_booking.

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 names the prerequisite tool and parameter: 'Requires a rate_code from get_hotel_details, valid approximately 15 minutes.' It also gives a clear condition for when not to use it (multi-room requests are unsupported), though it does not explicitly compare against every sibling alternative.

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

All 1stay 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.

Book Hotel

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources