Events.Aero

Search events

search-events

Read-onlyIdempotent

Search upcoming public aviation events on Events.Aero (airshows, fly-ins, workshops and more). Filter by free text, event type, country, date range, distance from a point, free entry or online events. Results are ordered by start date, or by distance when latitude and longitude are given, one page at a time. Every result includes the public event page URL: send people there to book or RSVP.

Input Schema

Name	Required	Description
`to`	No	Latest start date, YYYY-MM-DD, inclusive: a calendar date matched against each event's own local start date
`free`	No	Only free events
`from`	No	Earliest start date, YYYY-MM-DD: a calendar date matched against each event's own local start date (in the event's timezone)
`page`	No	Page of results, from 1
`type`	No	Event type, from list-event-types
`query`	No	Words matched against the event name, venue name, town and location: every word must appear, matched from the start of a word ("dux" finds Duxford); up to 100 characters
`online`	No	Only online events
`country`	No	Two-letter country code, e.g. GB: list-countries lists the live countries; a soft-launched country is answered only when named (without one, only live countries are searched)
`latitude`	No	Search near this point (with longitude); results are ordered by distance
`per_page`	No	Results per page (default 20, at most 50)
`longitude`	No	Search near this point (with latitude)
`radius_nm`	No	Radius around the point in nautical miles (default 50, at most 500)

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 11, 2026

changedInput schema / properties / query / description

Previous value: -"Free text matched against the event name, venue name, town and location (up to 100 characters)"New value: +"Words matched against the event name, venue name, town and location: every word must appear, matched from the start of a word (\"dux\" finds Duxford); up to 100 characters"

Changed1 schema field changedOct 10, 2026

changedInput schema / properties / type / enum

Previous value: -[
-  "airshow",
-  "fly_in",
-  "static_display",
-  "workshop",
-  "seminar",
-  "online_event",
-  "club_meet",
-  "conference",
-  "expo",
-  "competition",
-  "charity_event",
-  "military"
-]New value: +[
+  "airshow",
+  "fly_in",
+  "static_display",
+  "workshop",
+  "seminar",
+  "online_event",
+  "club_meet",
+  "conference",
+  "expo",
+  "competition",
+  "charity_event",
+  "military",
+  "spotting",
+  "model_aircraft"
+]

Changed1 schema field changedOct 10, 2026

changedInput schema / properties / type / enum

Previous value: -[
-  "airshow",
-  "fly_in",
-  "static_display",
-  "workshop",
-  "seminar",
-  "online_event",
-  "club_meet",
-  "conference",
-  "expo",
-  "competition",
-  "charity_event"
-]New value: +[
+  "airshow",
+  "fly_in",
+  "static_display",
+  "workshop",
+  "seminar",
+  "online_event",
+  "club_meet",
+  "conference",
+  "expo",
+  "competition",
+  "charity_event",
+  "military"
+]

Changed1 schema field changedOct 10, 2026

changedInput schema / properties / country / description

Previous value: -"Two-letter country code from list-countries, e.g. GB"New value: +"Two-letter country code, e.g. GB: list-countries lists the live countries; a soft-launched country is answered only when named (without one, only live countries are searched)"

First observedOct 9, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations only cover readOnlyHint and idempotentHint, and the description adds real behavior: results are ordered by start date (or by distance when coordinates are supplied), results are paginated 'one page at a time', and every result carries the public event page URL. It does not discuss rate limits or how soft-launched countries behave beyond what the schema says.

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?

Three sentences, front-loaded with the purpose, then filters, then output ordering and the booking-URL affordance; no filler and no repetition of schema text.

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

Completeness5/5

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

With no output schema, the description still tells the agent what comes back (ordered, paginated results containing the public event URL) and how to use it for booking, which is the key downstream action. For a 12-param read-only search whose parameters are fully schema-documented, nothing essential is missing.

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%, so each parameter — including date semantics, radius bounds, per_page limits and country soft-launch behavior — is already fully documented in the schema. The description's mention of ordering by distance when latitude/longitude are given largely duplicates the schema's own note, so it adds little beyond baseline.

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 and resource ('Search upcoming public aviation events on Events.Aero') and enumerates the filter dimensions (free text, type, country, date, distance, free, online), which is more than enough for an agent to distinguish it from featured-events and get-event.

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?

The description makes clear this is the filtered-search entry point and points to list-event-types and list-countries for valid enum/country values, giving clear context for use. It stops short of stating when to prefer featured-events or get-event instead, so no explicit alternative routing.

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

All Events.Aero 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?