Skip to main content
Glama

Fare Facts

Get a US air passenger right, with sources (free)

get_passenger_right
Read-onlyIdempotent

US airline passenger rights: the federal rule for one topic (for example refunds when a flight is cancelled, denied boarding, tarmac delays, the 24-hour rule, lost bags, wheelchairs), questions a passenger can raise with the airline, citations and a current-as-of date. It states rules only; it does not calculate bump payment amounts or explain ticket codes. 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": {
      "topic": "<topic>"
    },
    "name": "get_passenger_right"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicYesTopic id; the allowed ids are the values listed in this schema.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover read-only, closed-world, idempotent behavior, so the description correctly spends its space on non-obvious traits: no account required, everything free, answers carry a 'current-as-of' date, and no PII (names, record locators, ticket or frequent flyer numbers) is accepted or used. That privacy and freshness disclosure is genuinely additive; it stops short of describing answer length or citation format, which is a minor gap.

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 purpose, then scope limits, then the free/PII facts — a sensible order with no filler. The closing clause ('the input is only the codes or numbers in the input schema') partly repeats the preceding sentence about not needing names and record locators, so one small trim is possible.

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?

With no output schema, the description takes on the burden of describing returns and does so: federal rule for one topic, passenger questions, citations, and a currency date. Together with the free/no-account and no-PII disclosures, an agent has everything needed to call this correctly for a single-parameter read-only lookup.

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?

Schema coverage is 100% and the single parameter is a fully enumerated topic id, so the baseline is 3. The description adds value by mapping colloquial user requests ('refunds when a flight is cancelled', 'tarmac delays', 'lost bags') onto topics and by stating that no identifiers beyond the schema values are needed, reducing the temptation to pass passenger data.

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 ('US airline passenger rights: the federal rule for one topic') and enumerates concrete topics (refunds, tarmac delays, 24-hour rule, lost bags, wheelchairs). It also discloses exactly what comes back — the rule, questions a passenger can raise, citations, and a current-as-of date — and explicitly carves itself away from calculate_bump_compensation and explain_fare_basis/explain_tax_codes.

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?

Clear about what the tool is for and what it is not ('states rules only; it does not calculate bump payment amounts or explain ticket codes'), which implicitly routes agents to the calculator and fare-code siblings. It never names an alternative explicitly nor says whether list_rights_topics should be consulted first to pick a topic id, so the routing signal is inferential rather than direct.

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