Skip to main content
Glama

Opensky

by io.github.pipeworx-io

Get Flights

get_flights
Read-onlyIdempotent

Historical flight legs (departure and arrival airports) for a past time window. NOT AVAILABLE from a hosted environment: OpenSky is the only source of this data and it cannot be reached from cloud infrastructure, while the keyless ADS-B feeds that replace it carry live positions only. Returns an explicit not-available result naming what does work instead — live aircraft via get_states, a callsign's scheduled route via get_flight_route, and live airport activity via get_arrivals / get_departures in the flights pack.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endYesEnd of the interval, Unix seconds.
beginYesStart of the interval, Unix seconds.

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructiveness. The description adds crucial behavioral context: the data source constraint (OpenSky unreachable from cloud) and the fallback behavior (returns an explicit not-available result naming working alternatives). This goes beyond the annotations.

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?

The description is concise but dense, with each sentence serving a purpose: purpose first, then environment limitation, then fallback alternatives. No wasted words, and structure is logical.

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?

Despite no output schema, the description covers what the tool does, its constraints, and what to use instead in unsupported environments. It is complete for a tool with rich annotations and simple parameters.

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% with begin and end described as Unix seconds. The description adds 'past time window' but does not provide additional syntax or format details beyond the schema. Baseline 3 applies because the schema fully documents parameters.

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

Purpose5/5

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

The description clearly states the tool's function: 'Historical flight legs (departure and arrival airports) for a past time window.' It uses a specific verb and resource, and distinguishes itself from siblings by explicitly naming alternatives like get_states and get_flight_route.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly addresses when to use this tool (for historical data in a past time window) and when not (not available from hosted environments), and provides named alternatives: 'live aircraft via get_states, a callsign's scheduled route via get_flight_route...' This is clear usage guidance.

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

All Opensky toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation2/5

Several tools have heavily overlapping entry points: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, and validate_claim all take natural-language factual questions, and ask_pipeworx_beta is explicitly identical to ask_pipeworx right now. There is also overlap among get_states, get_aircraft, and airspace_activity, plus a large cluster of prediction-market tools with similar discovery purposes.

Naming Consistency4/5

The set is mostly snake_case and readable, with familiar patterns like get_*, list_*, resolve_*, and compare_*. It is not chaotic, but there are notable deviations: noun-phrase names like entity_profile, recent_changes, ai_visibility_check, and airspace_activity break the verb-first pattern.

Tool Count2/5

35 tools is too many for a single coherent server, especially because they comprise several independent families: aviation, data/research, prediction markets, memory, and subscriptions. Each tool is individually justified, but the bundle should be split into smaller focused MCP servers.

Completeness3/5

The data-research side is fairly complete, with discover, routing, grounded verification, entity resolution, search-within, compare, and follow-up tools, and the subscription and memory lifecycles are covered. However, the OpenSky side is incomplete: get_flights explicitly cannot return its data, and referenced route/arrival/departure tools are missing from the set.

Resources