Skip to main content
Glama

get_reservation_status

Read-onlyIdempotent

Return the current status and exact stay, price, payment schedule, and cancellation terms for a reservation previously created through ATA. Requires the hold ID plus the same verified traveler context/assertion or the secure booking handoff that created it. This tool is read-only and cannot change, pay, cancel, check in, or check out a reservation.

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": {
      "holdId": "<holdId>"
    },
    "name": "get_reservation_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
holdIdYesHold ID returned by create_provisional_booking.
guestEmailNoTraveler email. Required when using travelerAssertion; populated automatically for a verified MCP session.
propertyTokenNoKnown public property token for this reservation; must match the hold property when supplied.
agentHandoffIdNoSecure BOOKING_HOLD handoff ID that created this reservation.
displayCurrencyNoOptional 3-letter currency for approximate display conversion. Native property currency remains authoritative.
travelerAssertionNoCurrent signed ATA traveler verification assertion for the reservation guest.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / guestEmail / pattern
      Previous value: -"^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"New value: +"^(?:[A-Za-z0-9_'+\\-]+\\.)*[A-Za-z0-9_'+\\-]*[A-Za-z0-9_+-]@(?:[A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"
  2. Changed1 schema field changed
    • addedInput schema / properties / propertyToken
      Added value: +{
      +  "description": "Known public property token for this reservation; must match the hold property when supplied.",
      +  "type": "string"
      +}
  3. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is known. The description still adds real value by spelling out the authentication prerequisite and by explicitly enumerating the mutations it cannot perform (change, pay, cancel, check in, check out).

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?

Three sentences, front-loaded with what is returned, then prerequisites, then scope limits. Zero filler and every sentence carries actionable information.

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?

With no output schema, the description correctly enumerates the returned payload (status, exact stay, price, payment schedule, cancellation terms) and covers auth requirements and mutation limits. The main gap is that it does not clarify how this differs from get_booking_details, which matters given the sibling list.

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?

Schema coverage is 100%, so the baseline is 3. The description goes beyond the per-field schema text by clarifying the either/or relationship between travelerAssertion and agentHandoffId and by noting that the hold ID is required alongside that verified context, which helps an agent choose the right auth parameter.

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?

States a specific verb and resource: returns status plus stay, price, payment schedule, and cancellation terms for an ATA-created reservation. Clear on its own, but it never distinguishes itself from the close sibling get_booking_details, which an agent could easily confuse it with.

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?

Implies usage by scoping to reservations 'previously created through ATA' and by listing prerequisites (hold ID plus verified traveler context or booking handoff). It does not name an alternative or state when another tool should be preferred, leaving the get_booking_details boundary ambiguous.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources