flightaware-mcp

fa_create_alert

Create a flight alert to monitor a flight or route, with notifications for departure, arrival, diversion, cancellation, and other events. Requires Standard or Premium AeroAPI tier and user confirmation.

Instructions

Create a flight alert on your AeroAPI account. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview of the request (method, path, body) and a confirmToken, makes NO network call, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE). Requires a Standard or Premium AeroAPI tier (the free Personal tier returns 401).

Input Schema

TableJSON Schema

Name	Required	Description
`eta`	No	Notify on ETA changes
`hold`	No	Notify on hold
`filed`	No	Notify when a flight plan is filed
`ident`	No	Flight ident / designator to watch (e.g. UAL123)
`origin`	No	Origin airport code filter
`arrival`	No	Notify on arrival
`diverted`	No	Notify on diversion
`end_date`	No	ISO-8601 date the alert expires
`cancelled`	No	Notify on cancellation
`departure`	No	Notify on departure
`max_weekly`	No	Cap on notifications per week
`start_date`	No	ISO-8601 date the alert becomes active
`destination`	No	Destination airport code filter
`confirmToken`	No	ONLY for the two-step confirmation fallback (a client without MCP elicitation). The confirmToken from this same tool's phase-1 "confirmation-required" response, passed back ONLY after the user has seen that preview and explicitly approved it in chat — never on the first call, never invented, never reused. Call again with the same arguments. Ignored when the client supports elicitation.
`aircraft_type`	No	ICAO aircraft type filter (e.g. B738)

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.2.0Sep 24, 2026

removedInput schema / properties / confirm

Removed value: -{
-  "description": "Must be true to proceed. Without this, the tool returns a preview.",
-  "type": "boolean"
-}

addedInput schema / properties / confirmToken

Added value: +{
+  "description": "ONLY for the two-step confirmation fallback (a client without MCP elicitation). The confirmToken from this same tool's phase-1 \"confirmation-required\" response, passed back ONLY after the user has seen that preview and explicitly approved it in chat — never on the first call, never invented, never reused. Call again with the same arguments. Ignored when the client supports elicitation.",
+  "type": "string"
+}

Changed1 schema field changedv1.0.0Sep 19, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

First observedv0.1.0Jun 23, 2026

TDQS

A4.5/5.0

Behavior5/5

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

The description adds substantial behavioral context beyond the annotations: the two-step confirmation flow, the fact that the first call makes no network request, the confirmToken repeat-call requirement, and the 401 failure on the free tier. These details are not visible in readOnlyHint/openWorldHint/idempotentHint and significantly help an agent act correctly.

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?

The description is three sentences and front-loads the core purpose before the confirmation nuance. It is somewhat dense, especially the MCP_CONFIRM_MODE reference, but every sentence contributes necessary information and none is wasted.

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?

Given 15 parameters, no output schema, and sparse annotations, the description covers the most critical operational concerns: confirmation behavior, network-call semantics, token reuse, and auth requirements. It does not describe the final success response or which parameter combinations are required to actually create an alert, so it is not fully complete, but it is strong for the tool's complexity.

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 coverage is 100%, so the baseline is 3. The description adds real value beyond the schema by explaining the confirmToken protocol: it must not be sent on the first call, must not be invented or reused, and must accompany a repeat call with the same arguments. This is critical usage semantics that the schema alone does not fully convey.

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 opens with a specific verb and resource: 'Create a flight alert on your AeroAPI account.' This clearly distinguishes the tool from siblings like fa_update_alert, fa_delete_alert, and fa_list_alerts. The rest of the description reinforces the creation role with confirmation-flow details.

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 provides clear context for when to use the tool: creating a flight alert, requiring user confirmation, and needing a Standard or Premium tier. It does not explicitly point to alternative tools for update/delete/list operations, but the sibling names and the creation-focused wording make the intended use clear.

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

fa_create_alert

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools