Skip to main content
Glama

agent-exec

Where an aircraft is right now, by callsign, hex address or tail number (paid, x402)

flights_lookup
Read-only

PAID: look up a flight: where an aircraft is now (position, altitude, speed, track) by callsign, ICAO24 hex or tail number, $0.0100. Data: adsb.lol community ADS-B feed, ODbL 1.0. Unpaid, it returns the price; pay with x402 (USDC on Base, Solana, Polygon, Arbitrum, Avalanche, Sei or X Layer) in _meta['x402/payment'] and call again. Feedback: POST /feedback (free). Read daily; no individual reply.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "flights_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
identNoOne aircraft identifier: a callsign (UAL1), a 6-hex ICAO24 address (a0b1c2) or a registration (N12345, D-ABCD). Prefix cs:, hex: or reg: to say which kind it is -- unprefixed, a 6-hex-looking string is read as a CALLSIGN. Lowercase is fine.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations only cover read-only/non-destructive safety, and the description adds real behavior: a pay-per-call model with a two-step probe-then-pay flow, the upstream data source and ODbL licensing, and a feedback channel that explicitly says there is no individual reply. It does not state what happens on no-match or how stale a position might be, so a small gap remains.

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?

It is dense and front-loaded — price flag first, then what is returned, then the payment mechanics. The trailing feedback/"read daily" note is marginal for an invocation decision and slightly dilutes the payload, but 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?

For a one-parameter, annotated, output-schema-less tool it covers the essentials: cost, payment protocol, data provenance, and returned fields. The notable omissions are the response envelope shape and the failure/no-match behavior, which matter because no output schema exists.

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 100% and the single `ident` parameter already documents the cs:/hex:/reg: prefix convention and the 6-hex-looks-like-callsign rule. The description only restates the three identifier kinds, adding no syntax or format detail beyond the schema, so the baseline 3 applies.

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 names a specific verb and resource ("look up a flight: where an aircraft is now"), enumerates the returned fields (position, altitude, speed, track) and the three accepted identifier kinds (callsign, ICAO24 hex, tail number). No sibling tool in the list does anything similar, so an agent can route to it unambiguously.

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?

It gives an explicit operating procedure: the unpaid call returns the price, payment goes into _meta['x402/payment'], then call again — plus the accepted payment chains. There are no when-not-to-use statements or named alternatives, but no sibling overlaps, so the missing exclusions cost little.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.