Skip to main content
Glama

Live aircraft inside a lat/lon box from the public

travel_flightradar24_live_flights
Read-only

Live aircraft inside a lat/lon box from the public Flightradar24 feed: callsign, position, altitude (ft), speed (kts), heading, aircraft type, registration, origin/destination airport codes and on-ground flag. Position data is seconds old; the feed does not include every flight worldwide and has no key or history. 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": {
      "north": "<north>",
      "south": "<south>",
      "west": "<west>",
      "east": "<east>"
    },
    "name": "travel_flightradar24_live_flights"
  }
}

Input Schema

NameRequiredDescriptionDefault
eastYesRight edge longitude -180 to 180
westYesLeft edge longitude -180 to 180
limitNoMax flights returned, 1 to 200 (default 50)
northYesTop edge latitude -90 to 90
southYesBottom edge latitude -90 to 90, below north

Output Schema

NameRequiredDescriptionDefault
countNo
sourceNo
flightsNo
checkedAtNo
inBoxTotalNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered structurally. The description still adds real behavioral context beyond them: position freshness (seconds old), incomplete global coverage, absence of history, and a per-call price of $0.002 via x402 with failures not charged. That pricing and latency disclosure is genuinely useful and goes past the annotations, though the emphasis here is on cost and freshness rather than on operational behavior.

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?

Two sentences, front-loaded with the core action and scope, followed by payload contents and then constraints and pricing. Almost every clause earns its place. The field enumeration in the first sentence is long but useful for deciding fitness.

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?

An output schema exists, so return-value explanation is optional, and the tool's annotations plus full schema coverage carry most of the remaining load. The description covers freshness, coverage gaps, and payment model, which are the non-obvious risks for this tool. Minor omissions like rate limits or the meaning of the limit default are absorbed by the schema.

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 description coverage is 100%, so the five parameters (north, south, east, west, limit) are already fully documented with ranges and defaults in the input schema. The description restates the bounding-box concept but adds no syntax, ordering, or edge-case detail beyond what the schema provides. Baseline 3 is appropriate when the schema carries the parameter burden.

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 names a specific verb and resource: live aircraft positions fetched from the public Flightradar24 feed within a lat/lon bounding box. It also lists what comes back (callsign, altitude, speed, heading, registration, origin/destination), so an agent knows exactly what it gets. It stops short of naming a sibling such as travel_flightaware_public_tracker to distinguish itself from, which keeps it from a 5.

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 stated: the tool is for current aircraft inside a geographic box. The description does supply selection-relevant constraints (no history, feed does not cover every flight worldwide, no key needed), which help an agent decide whether it is appropriate. It never says when to prefer an alternative source, or when not to call it.

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