Threshold

Get booking status

get_booking

Read-only

Status, amounts, refund schedule, guest ID verification link, and when arrival details will be sent. Maps to GET /v1/bookings/{id}. Pass guest_email (the email the booking was made with) unless you connect with an agent token.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "booking_id": "<booking_id>"
    },
    "name": "get_booking"
  }
}

Input Schema

Name	Required	Description	Default
`booking_id`	Yes	The booking's id, from request_booking (starts with bkg_).
`guest_email`	No	The email the booking was made with. Needed unless you connect with an agent token.

Output Schema

Name	Required	Description
`id`	No
`total`	No	An amount in cents with its currency.
`status`	No	e.g. awaiting_payment, pending_host_confirmation, confirmed, declined, cancelled.
`check_in`	No
`check_out`	No
`property_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 23, 2026

addedInput schema / properties / guest_email

Added value: +{
+  "description": "The email the booking was made with. Needed unless you connect with an agent token.",
+  "format": "email",
+  "type": "string"
+}

Changed2 schema fields changedOct 14, 2026

addedInput schema / properties / booking_id / description

Added value: +"The booking's id, from request_booking (starts with bkg_)."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "The booking.",
+  "properties": {
+    "check_in": {
+      "type": "string"
+    },
+    "check_out": {
+      "type": "string"
+    },
+    "id": {
+      "type": "string"
+    },
+    "property_id": {
+      "type": "string"
+    },
+    "status": {
+      "description": "e.g. awaiting_payment, pending_host_confirmation, confirmed, declined, cancelled.",
+      "type": "string"
+    },
+    "total": {
+      "description": "An amount in cents with its currency.",
+      "properties": {
+        "amount": {
+          "type": "integer"
+        },
+        "currency": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

First observedOct 2, 2026

TDQS

A3.7/5.0

Behavior4/5

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

With readOnlyHint=true and destructiveHint=false already in annotations, the description adds useful context: it lists the returned information and states the authentication requirement for guest_email unless using an agent token. It does not cover error behavior or privacy constraints, but it meaningfully extends beyond annotations.

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 short and front-loads the most important return contents before the endpoint mapping and parameter note. It is efficient, though the opening noun-list fragment is slightly less direct than an explicit verb-led statement.

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?

The tool has an output schema, so return values do not need full explanation here, and annotations cover the safety profile. With only two parameters fully documented in the schema, the description is complete enough for correct invocation, with only minor gaps around error and edge-case behavior.

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 both parameters are already fully documented in the schema. The description's note about guest_email largely repeats the schema wording and adds no extra syntax or constraint beyond it, making the baseline 3 appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly identifies the booking resource and enumerates what is returned: status, amounts, refund schedule, guest ID verification link, and arrival details timing. It is specific enough to distinguish this from sibling tools like cancel_booking or get_quote, though it lacks an explicit verb and reads partly as a return-field list.

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

Usage Guidelines3/5

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

Usage is implied by the name and the field list, and the description gives the guest_email access condition. However, it does not explicitly say when to use this tool versus alternatives such as get_quote or get_messages, nor does it describe exclusions or prerequisites beyond the email/agent token note.

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

All Threshold 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?