Skip to main content
Glama
danmarce

adsb-mcp

by danmarce
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Aircraft near a point

aircraft_near
Read-onlyIdempotent

Find aircraft within a chosen radius of any latitude/longitude point and return them nearest first, using live ADS-B data without needing a receiver location.

Instructions

Aircraft currently within radius_km of a given point (lat/lon you supply — e.g. a city), nearest first. Unlike aircraft_overhead this needs no receiver location: distance is measured from the point you pass.

    Args:
        latitude/longitude: the centre point to search around.
        radius_km: search radius in kilometres (default 50).
        max_results: cap on aircraft returned (default 10).
        include_grounded: include aircraft on the ground (default False).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
latitudeYes
longitudeYes
radius_kmNo
max_resultsNo
include_groundedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the bar is lower, and the description still adds real behavioral context: results are ordered nearest-first and no receiver location is required. It does not disclose rate limits, empty-result behavior, or freshness of the live data.

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?

Purpose and sibling contrast are front-loaded in the first two sentences; the Args block is compact. It does restate defaults already present in the schema, which is mild redundancy but aids scanning.

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?

There is no output schema, and the description never says what is returned per aircraft or how an empty result is signalled, only the cap and ordering. For a read-only lookup tool the essentials for invocation are present, but the return contract is left implicit.

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 0%, so the description carries the burden and does compensate: all five parameters are explained, including units (kilometres) and defaults (50, 10, False) plus the meaning of include_grounded. It stops short of acceptable lat/lon ranges or format constraints.

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?

States a specific verb+resource+scope: 'Aircraft currently within radius_km of a given point', with explicit ordering ('nearest first'). It also names the sibling it differs from (aircraft_overhead), so an agent can distinguish the two without opening either schema.

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

Usage Guidelines4/5

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

Explicitly explains when this tool applies versus aircraft_overhead: it needs no receiver location because distance is measured from the supplied point. The find_aircraft sibling is never addressed, and there is no when-not-to-use guidance, so it stops short of a 5.

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

Deploy Server

Other Tools