Skip to main content
Glama

Public FlightAware flight page for one flight number

travel_flightaware_public_tracker
Read-only

Public FlightAware flight page for one flight number: airline, aircraft type, origin and destination airports (IATA, name), status (e.g. arrived, en route) and the flight ident. Read from the JSON embedded in the public page; no login. Live altitude and speed are not included on the page used. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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": {
      "ident": "<ident>"
    },
    "name": "travel_flightaware_public_tracker"
  }
}

Input Schema

NameRequiredDescriptionDefault
identYesFlight number such as UAL956 (2 to 8 letters and digits)

Output Schema

NameRequiredDescriptionDefault
identNo
originNo
sourceNo
statusNo
airlineNo
checkedAtNo
destinationNo
aircraftTypeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description goes well beyond them: it discloses the data source (JSON embedded in the public page), that no login is required, a hard data limitation (no live altitude/speed), and a billing model ($0.002 per successful call via x402, failures uncharged). That is exactly the extra context an agent needs before calling a paid, open-world read.

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 core purpose and returned fields are front-loaded, and the limitations and pricing follow in a compact sequence. It is slightly dense, packing source, limitations and payment into long clauses, but no sentence is disposable.

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 one-parameter read tool with an output schema and safety annotations, the description covers everything left open: source of truth, auth-free access, what the data does not contain, and the paid-call model including failure billing. Nothing an agent needs to invoke it correctly is missing.

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 single required parameter 'ident' is fully documented in the schema with an example format (UAL956). The description reinforces 'one flight number' but adds no format, normalization, or validation detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb+resource: 'Public FlightAware flight page for one flight number', and enumerates the returned fields (airline, aircraft type, origin/destination, status, ident). It implicitly distinguishes itself from live trackers by noting 'Live altitude and speed are not included', but never names an alternative tool, so sibling differentiation is suggested 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 context is implied: use this for static, per-flight reference data from a single flight number, and not for live altitude/speed. There is no explicit 'use X instead' routing or prerequisite statement, so the agent must infer the boundary with tools like live flight trackers or multi-flight searches.

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