flight-data

What is flying over me

aircraft_overhead

Read-only

Aircraft flying right now within radius_km (max 30) of a latitude/longitude, nearest first: callsign, type, altitude, speed. Free, no key.

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": {
      "lat": "<lat>",
      "lon": "<lon>"
    },
    "name": "aircraft_overhead"
  }
}

Input Schema

Name	Required	Description	Default
`lat`	Yes
`lon`	Yes
`radius_km`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Beyond the readOnlyHint annotation, the description discloses useful behavior: results are ordered nearest-first, the payload fields are enumerated, the query is free with no API key (an auth prerequisite), and the radius is capped at 30 km. It does not say what happens with zero matches or how many results can be returned, so it stops short of full disclosure.

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?

A single compact sentence that front-loads the resource and scope, then the return fields and the auth note. Every clause carries information and nothing is padded.

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?

With no output schema, listing the returned fields is exactly the right compensation, and the auth/cost note removes a common blocker. The remaining gap is result-size or empty-result behavior, which is minor for a simple read-only spatial query.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/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 carry the parameter burden, but it only restates the radius_km maximum that the schema already encodes as maximum: 30. It adds no meaning for lat/lon (units, format, decimal degrees, valid ranges) and no note on whether radius_km is in kilometers by default beyond the parameter name.

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 names a specific resource (aircraft flying right now), a spatial scope (within radius_km of a lat/lon), and the returned fields (callsign, type, altitude, speed). That is enough for an agent to tell it apart from historical siblings like flight_history or flight_on_date, though it never explicitly contrasts itself with the closely named live_aircraft_near.

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?

"Flying right now" implies a live-snapshot use case, which implicitly excludes the historical and lookup siblings, and the max-30 radius is stated. However, there is no explicit when-to-use/when-not-to-use statement and no guidance on choosing between this and the other live-position tools.

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

All flight-data tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?