Skip to main content
Glama
Sign In
@striderlabs/mcp-american

@striderlabs/mcp-american

by markswendsen-code
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

add_bags

Add checked baggage to an American Airlines booking by specifying the number of bags (1 or 2) and optionally a passenger name for group bookings.

Instructions

Add checked baggage to the booking. AA charges per bag per segment.

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": {
      "bags": "<bags>"
    },
    "name": "add_bags"
  }
}

Input Schema

NameRequiredDescriptionDefault
bagsYesNumber of checked bags to add (1 or 2)
passengerNoPassenger name if adding bags for a specific traveler in a group booking

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description must carry full behavioral disclosure. It states the action and a key business rule (AA charges per bag per segment), but it doesn't mention side effects like modifying the booking total, potential irreversibility, or permissions. It adds some value but leaves significant context undisclosed.

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 short sentences, immediately stating the purpose and a critical cost detail. No wasted words; front-loaded with the verb and object.

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?

For a simple two-parameter tool with full schema coverage, the description provides sufficient context: what it does, the cost rule, and implicit modification of a booking. It doesn't explain return values or error conditions, but given no output schema and low complexity, this is acceptable.

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 both 'bags' and 'passenger' described. The description adds no parameter-specific details beyond what the schema already provides. Baseline of 3 applies as the schema does the heavy lifting.

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 and resource: 'Add checked baggage to the booking.' It distinguishes itself from siblings by focusing on baggage addition, and the cost note adds clarity. No ambiguity.

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?

Usage is implied from the purpose—when one needs to add checked baggage—but there is no explicit guidance on when not to use it or mention of alternative tools. The description doesn't discuss prerequisites or relationship to sibling tools like modify_trip.

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

Deploy Server

Other Tools