Skip to main content
Glama

airport_movements

Retrieve estimated arrivals and departures for an airport over a short look-back window; ADS-B data infers origin or destination from first and last seen positions.

Instructions

List estimated arrivals and/or departures for an airport.

Each direction costs 4 OpenSky credits for a live window of under 24 hours.
OpenSky derives these movements from ADS-B, so they are estimates: the
origin/destination fields are inferred from the first and last seen position.

Args:
    airport: ICAO code, e.g. ESGG.
    direction: "arrival", "departure", or "both".
    window_minutes: Look-back window in minutes (5-60; OpenSky serves at most
        one hour of history).

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_movements"
  }
}

Input Schema

NameRequiredDescriptionDefault
airportYes
directionNoboth
window_minutesNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the credit cost per direction, a live-window limitation of under 24 hours, and the important caveat that origin/destination are inferred from first/last seen positions rather than reported. It does not mention authentication needs or rate limits beyond credits, and does not say what happens on invalid ICAO codes.

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 definition is front-loaded with purpose, then cost, then accuracy caveats, then an Args block — a clean structure with no filler. A sentence could be trimmed by merging the cost and data-quality notes, but nothing is wasted.

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 not required, and the description covers cost, freshness limits, accuracy caveats, and all three parameters. What remains unstated is whether 'both' doubles the credit cost and how errors (bad ICAO, excessive window) are surfaced, which matters for a pay-per-call tool.

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 coverage is 0%, so the description must compensate, and it largely does: it specifies airport as an ICAO code with an example, enumerates direction values ('arrival', 'departure', 'both') that the schema does not encode as an enum, and gives the 5-60 minute range for window_minutes. It omits the default of 60 for window_minutes and does not say which parameter is required.

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 opens with a specific verb+resource ('List estimated arrivals and/or departures for an airport'), which is clearly narrower than a sibling like airport_live_traffic. It never names an alternative, so differentiation is inferred from the 'estimated movements derived from ADS-B' framing rather than stated 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 implied by the cost note ('each direction costs 4 OpenSky credits') and the data-freshness constraint, which help an agent decide whether to spend the call. There is no explicit when-to-use versus when-not-to-use guidance and no reference to live-traffic or weather alternatives, so an agent must infer the tradeoff.

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