What's On Miami

Aircraft over Miami now

sky_now

Read-only

How many aircraft are over Miami right now, how many are private jets, and which airports they are arriving at or leaving (MIA, FLL, Opa-locka, Miami Executive, Fort Lauderdale Executive). Live from adsb.lol.

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already establish read-only, open-world, non-idempotent, non-destructive behavior. The description adds useful context beyond them: it is a live snapshot sourced from adsb.lol and returns counts plus airport arrival/departure information, though it does not discuss data completeness or private-jet classification caveats.

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 a single front-loaded sentence with no filler. The airport list is long but defines the geographic scope and earns its place.

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 zero-parameter tool with no output schema, the description does the important work of saying what is returned: aircraft counts, private-jet counts, and airports. It could be slightly more complete with data-freshness or coverage caveats, but it is sufficient for correct selection and invocation.

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?

The tool has zero parameters, so there is no parameter semantics burden. Baseline 4 is appropriate because there is no schema complexity for the description to compensate for.

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 states a specific live-data resource: aircraft currently over Miami, with counts, private-jet counts, and arrival/departure airports. It also names the data source, adsb.lol, so an agent can immediately distinguish this from the event/nightlife siblings.

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 phrase 'right now' implies this is for current snapshot questions rather than historical analysis, but there is no explicit when-to-use guidance, prerequisites, or comparison with alternatives. Usable but minimal.

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

All What's On Miami 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?