ATA Travel

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.

Input Schema

TableJSON Schema

Name	Required	Description
`holdId`	Yes	Hold ID returned by create_provisional_booking.
`guestEmail`	No	Traveler email. Required when using travelerAssertion; populated automatically for a verified MCP session.
`propertyToken`	No	Known public property token for this reservation; must match the hold property when supplied.
`agentHandoffId`	No	Secure BOOKING_HOLD handoff ID that created this reservation.
`displayCurrency`	No	Optional 3-letter currency for approximate display conversion. Native property currency remains authoritative.
`travelerAssertion`	No	Current signed ATA traveler verification assertion for the reservation guest.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 26, 2026

addedInput schema / properties / propertyToken

Added value: +{
+  "description": "Known public property token for this reservation; must match the hold property when supplied.",
+  "type": "string"
+}

AddedAug 29, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the annotations (readOnlyHint, idempotentHint, non-destructive), the description explicitly states the tool cannot change, pay, cancel, check in, or check out a reservation. It also discloses the authentication/context requirement, which is meaningful behavioral information the agent needs before calling.

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, each earning its place: what the tool returns, what it requires, and what it cannot do. The most important scoping information is front-loaded, and there is no redundancy with the schema or annotations.

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?

Even without an output schema, the description enumerates the returned content (status, stay, price, payment schedule, cancellation terms), covers prerequisites, and clarifies limitations. For a read-only lookup tool, this is sufficient for an agent to select and invoke it correctly.

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 adds semantic value by explaining that the hold ID must be paired with the same verified traveler context/assertion or the secure booking handoff that created the reservation, which clarifies the relationship between holdId, travelerAssertion, agentHandoffId, and guestEmail.

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 names a specific verb ('return') and a precise resource: the status, exact stay, price, payment schedule, and cancellation terms for an ATA-created reservation. This clearly separates it from quote, building, property, and traveler-verification tools among the siblings.

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 gives clear invocation context: it applies to reservations previously created through ATA and requires the hold ID plus a verified traveler context or secure booking handoff. It does not explicitly name alternative tools or state when not to use it, but the prerequisites and scope are unambiguous.

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

All ATA Travel 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?