@striderlabs/mcp-american

get_reservation

Look up an American Airlines reservation by record locator and passenger last name to retrieve booking details.

Instructions

Look up an existing American Airlines reservation by record locator (confirmation code).

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": {
      "recordLocator": "<recordLocator>"
    },
    "name": "get_reservation"
  }
}

Input Schema

Name	Required	Description	Default
`lastName`	No	Passenger last name (required for unauthenticated lookups)
`recordLocator`	Yes	The 6-character confirmation/record locator code (e.g., 'ABC123')

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 3, 2026

TDQS

B3.2/5.0

Behavior2/5

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

With no annotations, the description must disclose behavior, but it only states the lookup action. It does not mention whether authentication is required, that lastName is needed for unauthenticated lookups (though schema mentions), or what kind of data is returned. Lacks transparency about side effects or limitations.

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?

A single concise sentence that front-loads the purpose without unnecessary words. Every word contributes.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema, the description does not explain what the agent should expect as a return value (e.g., reservation details). It also lacks usage context such as preconditions like being logged in. The schema partially compensates by explaining lastName, but the description is incomplete for a tool that needs to be invoked correctly.

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?

The input schema fully describes both parameters with examples and notes on lastName requirement, so description adds no new semantic meaning. The mention of 'record locator' in the description is duplicated from the 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?

The description clearly states the tool's function with a specific verb 'look up' and resource 'existing American Airlines reservation', and identifies the key parameter 'record locator (confirmation code)'. This differentiates it from sibling tools like search_flights or get_flight_details.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives, such as using get_boarding_pass for boarding passes or check_in for check-in. There is no mention of exclusions or prerequisites.

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

Deploy Server