Skip to main content
Glama
thehesiod

aa-mcp-server

by thehesiod
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

get_reservation_by_locator

Retrieve complete reservation details using a 6-character record locator and lead passenger name. Get passengers, itinerary, tickets, cost summary, and change eligibility.

Instructions

Full reservation details by record locator + lead passenger name.

Returns the complete viewres payload: passengers (with passengerID like "01.01"), itinerary slices and segments (flight numbers, times, fare codes, booking codes), tickets (one per passenger), cost summary, eligibilityFlags (cancel / change / partial-reshop), and eligibleProducts (deep links to change-flow URLs).

The underlying endpoint validates first+last name against the lead passenger on the PNR, so both are required even when authenticated.

Args: record_locator: 6-character PNR (e.g., "UHJHHT"). last_name: Lead passenger last name (e.g., "Mohr"). first_name: Lead passenger first name (e.g., "Alexander"). account: Account name (optional, uses default).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
record_locatorYes
last_nameYes
first_nameYes
accountNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4.3/5.0
Behavior4/5

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

Describes validation of first+last name against lead passenger and lists return fields. Since no annotations exist, description carries burden; could explicitly state read-only but adequately covers behavioral aspects.

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?

Well-structured: summary, return contents, behavioral note, parameter list. Every sentence adds value with no redundancy.

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?

Comprehensive for a lookup tool; covers purpose, behavior, parameters, and return fields. Output schema exists so return details are bonus.

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?

With 0% schema coverage, description adds examples and explanations for all parameters (e.g., '6-character PNR', lead passenger name), significantly enhancing 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?

Clearly states 'Full reservation details by record locator + lead passenger name', specifying the verb, resource, and lookup method. Unique among siblings.

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 as a lookup tool but does not provide explicit when-to-use or alternatives. No exclusions or comparisons to sibling tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/thehesiod/aa-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server