Skip to main content
Glama

airport_live_traffic

Retrieve aircraft currently flying within a chosen radius of an airport, sorted by most recently heard, to monitor live local air traffic.

Instructions

Return aircraft currently within a radius of an airport.

Costs 1 OpenSky credit for a box up to 25 square degrees, up to 4 for a very
large radius. Aircraft are sorted by most recently heard.

Args:
    airport: ICAO code, e.g. ESGG.
    radius_nm: Search radius in nautical miles (5-200).
    max_aircraft: Cap on returned aircraft (1-200).

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": {
      "airport": "<airport>"
    },
    "name": "airport_live_traffic"
  }
}

Input Schema

NameRequiredDescriptionDefault
airportYes
radius_nmNo
max_aircraftNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does real work: it discloses the OpenSky credit cost model (1 credit up to 25 square degrees, up to 4 for a large radius) and the sort order (most recently heard first). It does not mention authentication or error behavior, but the cost/limit disclosure is the information an agent most needs before calling.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One-line purpose sentence, then a compact cost/sort note, then a terse Args block. Every sentence carries distinct information and the purpose is front-loaded.

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?

Three parameters, one required, an output schema already covering return values, and no annotations. The description supplies the purpose, the cost model, the ordering, and constraints for every parameter, so 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.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate, and it does: ICAO code with an example (ESGG), radius in nautical miles bounded 5-200, and max_aircraft bounded 1-200. It omits the defaults (40 and 40) that appear only in the schema, which keeps it short of a 5.

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 and resource: 'Return aircraft currently within a radius of an airport.' An agent can tell this is a live-position query rather than a schedule or history tool. It stops short of naming a sibling like airport_movements to draw the boundary explicitly.

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 only implied by the phrase 'currently within a radius' and the credit-cost note. There is no statement of when to pick this over airport_movements or how it combines with resolve_airport, and no exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.