Skip to main content
Glama

Fare Facts

Calculate US denied boarding (bump) compensation (free)

calculate_bump_compensation
Read-onlyIdempotent

US airline passenger rights: denied boarding compensation calculator for an involuntary bump from an oversold flight under 14 CFR 250.5. Returns the tier (0%, 200% or 400%), the formula result and the cap applied, the right to cash instead of a voucher, the exceptions, and the regulation's definition of fare. It covers involuntary bumps only, not volunteers, who negotiate their own deal with the airline. Free: every Fare Facts tool and answer is free, with no account. Names, confirmation codes (record locators), ticket numbers and frequent flyer numbers are not needed or used; the input is only the codes or numbers in the input schema.

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": {
      "one_way_fare_usd": "<one_way_fare_usd>",
      "route": "<route>"
    },
    "name": "calculate_bump_compensation"
  }
}

Input Schema

NameRequiredDescriptionDefault
routeYesdomestic = within the US; international_from_us = an international flight departing a US airport.
one_way_fare_usdYesOne-way fare in US dollars to the passenger's destination or first stopover (a planned break of more than 4 hours), including all mandatory taxes and fees but not optional extras such as seat or bag fees. This is how 14 CFR 250.1 defines "fare". An award or other zero-fare ticket is 0.
alternate_arrival_delay_hoursNoHow many hours after the original flight's planned arrival the alternate flight the airline offered is planned to arrive (at the destination or first stopover). Omitted when no alternate flight was offered.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, but the description goes further by enumerating what the calculation returns (tier 0/200/400%, formula result, cap applied, cash-vs-voucher right, exceptions, fare definition). It also discloses cost/auth ('free... no account') and a privacy trait ('names, confirmation codes, ticket numbers and frequent flyer numbers are not needed or used').

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the regulation and scenario, then the return payload, then the scope exclusion, then the free/no-PII boilerplate. The closing sentence about free access and unused identifiers is somewhat promotional and repeats the privacy point, costing a little tightness.

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?

There is no output schema, and the description compensates by listing exactly what comes back (tier, formula, cap, cash right, exceptions, fare definition). Combined with the scope exclusion and the no-PII note, an agent has everything needed to decide and invoke correctly for this simple three-parameter read-only calculator.

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% and the schema already carries the important semantics, including the 14 CFR 250.1 fare definition, the first-stopover rule, and the zero-fare case. The description reinforces that only schema inputs are used and no PII is expected, but adds no new meaning about route, fare, or the optional delay parameter, so the baseline 3 applies.

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?

States a specific verb and resource ('denied boarding compensation calculator') with the governing regulation (14 CFR 250.5) and the precise scenario (involuntary bump from an oversold flight). It explicitly delimits scope against the nearby concept of volunteers, so an agent can separate it from the explain_/get_/list_ siblings without opening a schema.

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?

Gives clear when-to-use context (involuntary denied boarding under 14 CFR 250.5) and an explicit when-not ('covers involuntary bumps only, not volunteers, who negotiate their own deal'). It stops short of naming a sibling alternative such as get_passenger_right for the general rights question, so routing between tools is implied rather than fully spelled out.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources