flight-data

Aircraft over a place

overhead_summary

How many aircraft passed within km of a point over the last 1 to 3 days: passes per day, lowest pass, busiest hour (UTC), night passes, types, operators, rarest visitor. 20 credits.

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": "overhead_summary"
  }
}

Input Schema

Name	Required	Description	Default
`km`	No
`lat`	Yes
`lon`	Yes
`days`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

B3.3/5.0

Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose the hard window limit (1-3 days) and the cost (20 credits), which is genuinely useful, but says nothing about whether the operation is read-only, whether it needs an API key or rate limit, how missing/remote locations behave, or what the aggregation tolerates.

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 front-loaded sentence defining the computation, followed by a compact colon-delimited list of returned fields and a cost token. Every clause carries information an agent cannot get elsewhere; nothing is redundant.

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 no output schema, the description sensibly enumerates the returned fields, and with no annotations it adds the credit cost and time window. Gaps remain for a data-query tool: coordinate expectations, whether results are bucketed or empty when nothing passed, and freshness of the underlying data are unstated.

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 description coverage is 0%, and the prose compensates reasonably: 'within km of a point' identifies km as a radius around lat/lon, and 'over the last 1 to 3 days' identifies days as a lookback window. It does not clarify coordinate format/units, default values, or the 1-10 km / 1-3 day bounds, so the schema still supplies the operational detail.

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?

States a specific resource and operation: an aggregate count of aircraft passes within a radius of a point over a 1-3 day lookback, and enumerates what the summary contains (passes per day, lowest pass, busiest hour, night passes, types, operators, rarest visitor). It is clearly distinguishable from live-listing siblings by the word 'summary' and the historical window, though it never names a sibling to contrast with.

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 only implied: the word 'summary' plus 'over the last 1 to 3 days' signals this is for historical statistics rather than live tracking or a specific flight lookup. There is no explicit when-to-use/when-not statement, no named alternative (e.g. aircraft_overhead or live_aircraft_near), and no note about prerequisites.

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?