Snapstay

Get a booking at the selected hotel by its ID

bookings.get

Read-onlyIdempotent

Get a booking at the selected hotel by its ID. Use bookings.list to find the ID by guest name, email, or booking code. Use guests.bookings for a guest's booking history.

Input Schema

Name	Required	Description	Default
`id`	Yes	Booking record ID from bookings.list or guests.bookings.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 25, 2026

addedOutput schema / properties / result / properties / booking / properties / products

Added value: +{
+  "description": "Active extras and fees. Prices and totals use the booking currency.",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "bookingUnitId": {
+        "type": "string"
+      },
+      "mode": {
+        "enum": [
+          "once",
+          "per_night",
+          "per_person",
+          "per_person_per_night"
+        ],
+        "type": "string"
+      },
+      "name": {
+        "type": "string"
+      },
+      "price": {
+        "type": "string"
+      },
+      "quantity": {
+        "type": "number"
+      },
+      "total": {
+        "type": "string"
+      },
+      "type": {
+        "enum": [
+          "product",
+          "fee"
+        ],
+        "type": "string"
+      }
+    },
+    "required": [
+      "name",
+      "type",
+      "mode",
+      "price",
+      "quantity",
+      "total"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

Changed2 schema fields changedOct 23, 2026

addedOutput schema / properties / result / properties / booking / properties / units / items / properties / stayStatus
```
Added value: +{
+  "enum": [
+    "booked",
+    "staying",
+    "completed"
+  ],
+  "type": "string"
+}
```

changedOutput schema / properties / result / properties / booking / properties / units / items / required

Previous value: -[
-  "unitId",
-  "checkinAt",
-  "checkoutAt",
-  "guests"
-]New value: +[
+  "unitId",
+  "stayStatus",
+  "checkinAt",
+  "checkoutAt",
+  "guests"
+]

Changed1 schema field changedOct 23, 2026

changedInput schema / properties / id / description

Previous value: -"ID of the record to get or change."New value: +"Booking record ID from bookings.list or guests.bookings."

Changed2 schema fields changedOct 18, 2026
- addedInput schema / properties / id / description
```
Added value: +"ID of the record to get or change."
```
- addedOutput schema / properties / result / required
```
Added value: +[
+  "booking"
+]
```

Changed2 schema fields changedOct 17, 2026

added

Output schema / properties / result / properties / booking / properties / units / items / properties / cancellationPolicy

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "enabled": {
+      "type": "boolean"
+    },
+    "noshow": {
+      "additionalProperties": false,
+      "properties": {
+        "type": {
+          "type": "string"
+        },
+        "value": {
+          "type": "number"
+        }
+      },
+      "required": [
+        "type"
+      ],
+      "type": "object"
+    },
+    "presetId": {
+      "type": "string"
+    },
+    "tiers": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "minDays": {
+            "type": "number"
+          },
+          "penalty": {
+            "additionalProperties": false,
+            "properties": {
+              "type": {
+                "type": "string"
+              },
+              "value": {
+                "type": "number"
+              }
+            },
+            "required": [
+              "type"
+            ],
+            "type": "object"
+          }
+        },
+        "required": [
+          "minDays",
+          "penalty"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "enabled",
+    "tiers",
+    "noshow"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / result / properties / booking / properties / units / items / properties / id
```
Added value: +{
+  "type": "string"
+}
```

First observedOct 17, 2026

TDQS

A4.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds the 'selected hotel' scoping context but does not discuss behavior when the ID is missing, not found, or unauthorized, nor does it describe the returned record. With annotations carrying most behavioral weight, 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?

The definition is two sentences, front-loaded with the action and followed by precise sibling-routing guidance. Every sentence earns its place with no repetition or filler.

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?

The tool has a complete input schema and an output schema, so return values need not be explained in the description. Annotations cover safety and determinism, and the description covers the key retrieval workflow and alternatives. Nothing an agent needs in order to select and invoke it correctly 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%, and the schema already documents the single id parameter as coming from bookings.list or guests.bookings. The description reinforces that source in prose but adds no syntax, format, or validation detail beyond the schema. Baseline 3 is appropriate.

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 and resource: get a booking by its ID at the selected hotel. It also names sibling tools and clarifies the different retrieval paths, so an agent can distinguish it from bookings.list and guests.bookings without opening schemas.

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?

It explicitly says to use bookings.list when the ID must first be found by guest name, email, or booking code, and to use guests.bookings for a guest's booking history. This gives clear routing guidance among siblings.

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

All Snapstay 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.

Resources

Need Help?