Globalpulse-MCP

OpenSky — Live Flights in Region

globalpulse_aviation_get_live_flights

Read-only

Track real-time aircraft positions, altitude, speed, and heading within any geographic bounding box using live ADS-B data.

Instructions

Live ADS-B flight tracking for any geographic bounding box. Real-time position, altitude, speed, heading. Args: min_latitude, max_latitude, min_longitude, max_longitude, limit, on_ground_only, response_format India box: min_lat=8, max_lat=37, min_lon=68, max_lon=97.5 | Europe: min_lat=36, max_lat=71, min_lon=-10, max_lon=25

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": {
      "min_latitude": "<min_latitude>",
      "max_latitude": "<max_latitude>",
      "min_longitude": "<min_longitude>",
      "max_longitude": "<max_longitude>"
    },
    "name": "globalpulse_aviation_get_live_flights"
  }
}

Input Schema

Name	Required	Default
`limit`	No
`max_latitude`	Yes
`min_latitude`	Yes
`max_longitude`	Yes
`min_longitude`	Yes
`on_ground_only`	No
`response_format`	No	markdown

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 28, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations indicate read-only and non-destructive behavior. The description adds that tracking is real-time and covers position, altitude, speed, and heading, and mentions optional filters like on_ground_only and response_format. No contradictions, but could mention data source limitations (ADS-B coverage).

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 description is concise, with a clear purpose sentence followed by argument list and practical examples. The examples add useful context but slightly increase length; overall well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 7 parameters and no output schema, the description provides usage examples but does not describe the return format or fields beyond listing altitude, speed, etc. It lacks details on pagination or data completeness, leaving the agent partially uninformed.

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 has 0% description coverage. The description lists parameter names and provides example bounding box values, which adds some meaning but does not explain each parameter's specific purpose or constraints (e.g., limit maximum, on_ground_only effect).

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 live ADS-B flight tracking for a geographic bounding box, with specific data fields. It distinguishes itself from the sibling tool 'get_flights_by_country' which focuses on country-level filtering.

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?

The description includes example bounding boxes for India and Europe, implying usage for regional tracking. However, it does not explicitly state when to prefer this tool over alternatives like 'get_flights_by_country' or when not to use it.

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

Deploy Server