Skip to main content
Glama

Fare Facts

Get an airline's missing miles request link (free)

get_missing_miles_link
Read-onlyIdempotent

US airline frequent flyer programs: where and how to request missing miles or points for a past flight (American, Delta, United, JetBlue, Alaska/Hawaiian, Southwest, Frontier, Spirit), with the waiting period, deadline, login needs and a basic economy caveat. Passenger rights rules are not covered. 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": {
      "airline": "<airline>"
    },
    "name": "get_missing_miles_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
airlineYesThe airline whose program you are asking about.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

The annotations already declare read-only, non-open-world, idempotent behavior, and the description adds useful context beyond them: the tool is free, requires no account, and does not need or use names, confirmation codes, ticket numbers, or frequent flyer numbers. It also discloses the kind of information returned, such as waiting periods, deadlines, login needs, and a basic economy caveat. It does not specify the exact response format, but it substantially supplements the annotations.

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?

The description is front-loaded with the core purpose and then adds useful exclusions and privacy context. It is generally efficient, though listing every airline duplicates the schema enum and the phrase about the input being 'only the codes or numbers in the input schema' is slightly awkward. Overall it remains readable and focused.

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 single-parameter lookup tool with rich annotations, the description covers scope, supported airlines, exclusions, privacy constraints, and the kinds of details the answer includes. The main remaining gap is that it does not precisely describe the return format, such as whether the result is a link, text, or structured details. That gap is minor but prevents a 5.

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 schema has one required parameter, airline, with 100% description coverage and an enum listing all supported values. The description repeats the airline list and clarifies that no personal data is needed, but it adds no semantics about the parameter beyond what the schema already provides. With full schema coverage, the baseline of 3 is appropriate.

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 states a specific resource and outcome: where and how to request missing miles or points for a past flight, for a defined list of US airlines. It also explicitly excludes passenger rights rules, distinguishing it from sibling tools like get_passenger_right and list_rights_topics. An agent can identify the tool’s scope without opening the 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?

The description gives clear context for when to use it: missing miles or points for a past flight on one of the listed US airline programs. It also states an exclusion, 'Passenger rights rules are not covered,' which implicitly routes those cases elsewhere. It does not explicitly name alternative sibling tools, but the usage context is strong.

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