Skip to main content
Glama

Fare Facts

List US air passenger rights topics (free)

list_rights_topics
Read-onlyIdempotent

US airline passenger rights: list the topics Fare Facts covers (bumping/denied boarding, refunds for cancellations and schedule changes, delays, meals and hotels, tarmac delays, the 24-hour rule, bag fees, lost or damaged bags, bag tracing, wheelchairs and mobility devices, what sellers must disclose before you buy, and pending rule changes), each with its topic id and a one-line summary. Free: every Fare Facts tool and answer is free, with no account. Takes no input.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_rights_topics"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false and idempotentHint=true, so the safety profile is covered. The description adds genuinely new context the annotations do not carry: that the tool and all answers are free, that no account is required, and the exact shape of each returned item (topic id plus one-line summary).

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 purpose and resource, followed by the return shape and cost/auth facts, with zero filler. The long parenthetical topic enumeration is dense but each item is a genuinely discoverable topic that helps an agent match a user question, so it earns its space; splitting it into a separate sentence would read more cleanly.

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?

For a zero-parameter, read-only listing tool with no output schema, the description supplies everything needed: what is listed, what each item contains, that no input is required, and that it is free with no account. Nothing an agent needs in order to call it correctly is missing.

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?

There are zero parameters, so the baseline is 4, and the description appropriately confirms 'Takes no input', which matches the empty schema with additionalProperties=false. No further parameter meaning is needed or offered.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb ('list') and resource ('topics Fare Facts covers') and enumerates the topic domains, so an agent knows this is a discovery/index tool rather than a detail lookup. It stops short of naming the sibling it complements (get_passenger_right), so the differentiation is inferable from the list-vs-get distinction rather than stated.

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 rather than prescribed: the return of 'topic id and a one-line summary' signals this is the first step before fetching a specific topic, and 'Takes no input' confirms it is a zero-argument entry point. There is no explicit when-to-use statement or a named alternative for going deeper once a topic id is in hand.

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