@striderlabs/mcp-american

select_seats

Choose seats for passengers on a flight. Check the seat map for availability, then reserve specific seats by seat number.

Instructions

Choose seats for passengers on the selected flight. Use get_seat_map first to see available seats.

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": {
      "seats": "<seats>"
    },
    "name": "select_seats"
  }
}

Input Schema

Name	Required	Description	Default
`seats`	Yes	List of seat numbers to select (e.g., ['14A', '14B'])
`flightNumber`	No	Optional flight number for multi-segment trips

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 3, 2026

TDQS

A3.7/5.0

Behavior2/5

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

No annotations are provided, so the description must disclose side effects. It implies a mutation (selecting seats) but does not state whether it is reversible, requires payment, or how it affects the reservation. Only the prerequisite of viewing the seat map is mentioned.

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?

The description is two sentences, front-loaded with purpose and a useful pointer to get_seat_map. No wasted words or redundant information.

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

Completeness3/5

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

The tool is simple with clear parameters, but the lack of annotations and output schema means the description should explain outcomes or side effects. It provides the essential workflow but leaves gaps about post-selection 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 coverage is 100% with descriptions for both parameters. The description adds no additional parameter detail beyond the schema, so it meets the baseline for high schema coverage.

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 uses a specific verb 'Choose' with a clear resource 'seats for passengers' and ties it to the selected flight, making it distinct from siblings like get_seat_map (viewing) and select_flight (choosing the flight).

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?

It explicitly instructs to use get_seat_map first, establishing a clear prerequisite and sequencing. It does not mention exclusions or alternative tools beyond that, but the context is sufficient for basic usage.

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

Deploy Server