Skip to main content
Glama
chrischall

flightaware-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

fa_get_airport_flight_counts

Read-only

Retrieve current flight counts for an airport: departed, enroute, scheduled arrivals, and scheduled departures. Get real-time traffic status to monitor airport activity.

Instructions

Get current flight counts at an airport: { departed, enroute, scheduled_arrivals, scheduled_departures }.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesAirport code (ICAO/IATA/LID)
viewNoResponse shape: "compact" (default) drops fields the response already carries elsewhere; "full" returns every field this server understands. compact strips image/avatar URLs from the response; "full" returns FlightAware's payload untouched. No field projection: this server has no verified record of which FlightAware fields matter, and inventing one would risk dropping a field a caller needs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed1 schema field changedv0.5.2
    • addedInput schema / properties / view
      Added value: +{
+  "description": "Response shape: \"compact\" (default) drops fields the response already carries elsewhere; \"full\" returns every field this server understands. compact strips image/avatar URLs from the response; \"full\" returns FlightAware's payload untouched. No field projection: this server has no verified record of which FlightAware fields matter, and inventing one would risk dropping a field a caller needs.",
+  "enum": [
+    "compact",
+    "full"
+  ],
+  "type": "string"
+}
  3. Addedv0.2.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations provide readOnlyHint=true and openWorldHint=true. The description adds context about the response shape (specifically the metrics returned) and the schema's description of 'view' adds behavioral detail about field projection and the risk of dropping fields, which goes beyond annotations.

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 a single concise sentence that front-loads the key purpose and metrics. It avoids fluff, though it could be slightly more structured to note input requirements, but it's already efficient.

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 read-only count tool, the description is sufficient to understand what it returns. The schema explains both parameters fully. No output schema, but the returned fields are enumerated. Potential missing info like exact response format is minor given the low complexity.

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 covers parameters 100%: 'id' has a pattern and description, 'view' explains the enum options in detail. The description slightly adds by listing the metrics, but the schema already explains the 'view' parameter's purpose comprehensively.

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 clearly states the tool retrieves current flight counts at an airport, listing the exact metrics returned (departed, enroute, scheduled_arrivals, scheduled_departures). It distinguishes from sibling tools like fa_get_airport, fa_get_airport_delays, and flight-specific tools by focusing on aggregate counts.

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 it's for aggregate counts at an airport but doesn't explicitly state when to use this vs. alternatives like fa_get_airport_flights which might list flights. However, the metric names clarify its purpose for counts, and the schema description for 'view' provides usage guidance on response shape.

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