Skip to main content
Glama
Sign In
ADSBiq MCP Server

ADSBiq MCP Server

by Sky-Power-Services
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_aircraft

Retrieve the current public state for any aircraft by providing its ICAO hex code. Useful for checking live position and status from ADSBiq community data.

Instructions

Get current public state for one ICAO hex aircraft.

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": {
      "hex": "<hex>"
    },
    "name": "get_aircraft"
  }
}

Input Schema

NameRequiredDescriptionDefault
hexYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden. It communicates that the operation is a read ('Get'), scoped to current public state, but it does not disclose response contents, staleness, error behavior, or any access caveats beyond 'public.'

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?

The description is one sentence with no filler. The core action and object are front-loaded, and every word contributes.

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?

For a one-parameter tool this is close to adequate, but 'state' is left vague and there is no output schema to explain the return value. It also doesn't mention the sibling alternatives, so the description leaves some context missing.

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 description coverage is 0%, so the description must compensate. It does so by identifying the lone parameter as an ICAO hex aircraft identifier, adding semantic meaning beyond the raw hex pattern in the schema.

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 uses a specific verb, 'Get,' names the resource, 'current public state for one ICAO hex aircraft,' and clearly scopes the operation to a single aircraft. This distinguishes it from the sibling tools, which concern nearby aircraft and network stats.

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 implies when to use the tool: when the agent has a specific ICAO hex and wants its current public state. It does not explicitly mention alternatives or state when not to use it, so guidance is implied rather than explicit.

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