Skip to main content
Glama

The Clearing — The Lantern & Consensual Agent Lab

query_airspace_radio_observatory

Reads the bounded Zero-PII Protocol AO-064 telemetry summary across ADS-B OSINT bots, WebSDR/radio-to-Whisper scanners, ACARS/METAR decoders, and locked MAVLink/AIS traps.

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

Input Schema

NameRequiredDescriptionDefault
window_hoursNoLookback window between 1 and 168 hours.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does contribute real behavioral signals: 'Reads' implies a non-mutating operation, 'Zero-PII' states a privacy guarantee about the returned data, and 'bounded' hints at a constrained query scope. It still omits return shape, whether data is live or cached, any auth/rate-limit constraints, and what 'locked ... traps' means operationally.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single sentence with no filler, which is good, but it front-loads dense jargon rather than the plain-language purpose. The four-source enumeration is the most informative part yet arrives after opaque protocol labels, so the structure obscures rather than clarifies.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with no annotations, no output schema, and an unexplained domain vocabulary, the description does not say what a 'telemetry summary' contains or how the four source families are combined. An agent could call it with a window but could not predict or interpret the result, leaving a substantive gap.

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%, with window_hours fully documented as a 1–168 hour lookback, so the baseline of 3 applies. The description adds only the word 'bounded' and does not clarify default behavior when the single optional parameter is omitted or how the window affects the summary.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a concrete verb ('Reads') and names a resource ('bounded Zero-PII Protocol AO-064 telemetry summary'), and it enumerates the four source families covered (ADS-B, WebSDR/radio-to-Whisper, ACARS/METAR, MAVLink/AIS). However, the core nouns ('AO-064', 'Zero-PII Protocol', 'locked ... traps') are unexplained internal jargon, so an agent cannot confidently tell what data is actually returned or how this differs from sibling observatory queries such as query_cross_science_observatory.

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

Usage Guidelines2/5

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

There is no statement of when to use this tool, when not to, or which sibling to prefer for adjacent questions. The list of data sources implies coverage but gives no selection criteria, and nothing indicates preconditions or prerequisites for calling it.

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.

Resources