Skip to main content
Glama

Opensky

by io.github.pipeworx-io

Airspace Activity

airspace_activity
Read-onlyIdempotent

Summary of live flight activity over a named region — aircraft count, country-of-registration breakdown, average altitude, and airborne vs on-ground split. Built for "is this airspace still operating" questions (airspace closures, conflict zones, strait and corridor traffic). Keyless. Supported regions: Iran, Israel, Syria, Ukraine, Russia, Taiwan, North Korea, South China Sea, Yemen, Strait of Hormuz, Taiwan Strait, Red Sea, Saudi Arabia, Gulf of Aden, Lebanon.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
regionYesRegion name, case-insensitive. For a custom area use opensky_get_states with lat/lon/radius_nm.

TDQS

A4.7/5.0
Behavior4/5

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

Beyond the annotations (readOnly, openWorld, idempotent), the description discloses that the tool is 'Keyless' and provides live summary data over a limited set of named regions. It also specifies the output components (count, breakdown, altitude, split), adding useful behavioral context without contradicting 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 two well-structured sentences: the first defines what the tool does and returns, the second gives use cases, keyless status, and supported regions. Every sentence earns its place with no fluff.

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 single-parameter tool with clear annotations and no output schema, this description is complete. It conveys the metrics returned, the intended use cases, the region constraints, and points to an alternative for custom areas, leaving minimal ambiguity for an agent.

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 100% and already describes the region parameter as case-insensitive and suggests an alternative for custom areas. The description further adds the list of supported regions, which is essential for selecting valid parameter values, thus going beyond the schema.

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 provides a 'Summary of live flight activity over a named region' with specific metrics (aircraft count, country breakdown, altitude, airborne/on-ground split). It distinctively positions itself for 'is this airspace still operating' questions, distinguishing it from sibling tools like get_states or get_flights.

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?

Explicitly states the tool is 'Built for "is this airspace still operating" questions (airspace closures, conflict zones, strait and corridor traffic)' and lists supported regions. The parameter schema adds 'For a custom area use opensky_get_states with lat/lon/radius_nm,' providing a clear alternative for out-of-list regions.

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