Skip to main content
Glama
cheesejaguar

Aerospace MCP

by cheesejaguar
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

plan_flight

Calculate a flight route between two airports with performance estimates, including waypoints and distances.

Instructions

Plan a flight route between two airports with performance estimates.

Args: departure: Dict with departure info (city, country, iata) arrival: Dict with arrival info (city, country, iata) aircraft: Optional aircraft config (ac_type, cruise_alt_ft, route_step_km) route_options: Optional route options

Returns: JSON string with flight plan details including departure/arrival airports, route waypoints, distances, and optional performance estimates.

Raises: No exceptions are raised directly; errors are returned as formatted strings. Internally catches AirportResolutionError and OpenAPError.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
departureYes
arrivalYes
aircraftNo
route_optionsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed21 schema fields changedv1.0.0
    • addedInput schema / properties / aircraft / anyOf
      Added value: +[
+  {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / aircraft / default
      Added value: +null
    • removedInput schema / properties / aircraft / properties
      Removed value: -{
-  "cruise_altitude": {
-    "default": 35000,
-    "description": "Cruise altitude in feet",
-    "maximum": 45000,
-    "minimum": 8000,
-    "type": "integer"
-  },
-  "mass_kg": {
-    "description": "Aircraft mass in kg (optional, uses 85% MTOW if not specified)",
-    "type": "number"
-  },
-  "type": {
-    "description": "ICAO aircraft type (e.g., 'A320', 'B738', 'A359')",
-    "type": "string"
-  }
-}
    • removedInput schema / properties / aircraft / required
      Removed value: -[
-  "type"
-]
    • addedInput schema / properties / aircraft / title
      Added value: +"Aircraft"
    • removedInput schema / properties / aircraft / type
      Removed value: -"object"
    • addedInput schema / properties / arrival / additionalProperties
      Added value: +true
    • removedInput schema / properties / arrival / properties
      Removed value: -{
-  "city": {
-    "description": "Arrival city name",
-    "type": "string"
-  },
-  "country": {
-    "description": "Arrival country code (optional)",
-    "type": "string"
-  },
-  "iata": {
-    "description": "Preferred arrival IATA code (optional)",
-    "type": "string"
-  }
-}
    • removedInput schema / properties / arrival / required
      Removed value: -[
-  "city"
-]
    • addedInput schema / properties / arrival / title
      Added value: +"Arrival"
    • addedInput schema / properties / departure / additionalProperties
      Added value: +true
    • removedInput schema / properties / departure / properties
      Removed value: -{
-  "city": {
-    "description": "Departure city name",
-    "type": "string"
-  },
-  "country": {
-    "description": "Departure country code (optional)",
-    "type": "string"
-  },
-  "iata": {
-    "description": "Preferred departure IATA code (optional)",
-    "type": "string"
-  }
-}
    • removedInput schema / properties / departure / required
      Removed value: -[
-  "city"
-]
    • addedInput schema / properties / departure / title
      Added value: +"Departure"
    • addedInput schema / properties / route_options / anyOf
      Added value: +[
+  {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / route_options / default
      Added value: +null
    • removedInput schema / properties / route_options / properties
      Removed value: -{
-  "step_km": {
-    "default": 25,
-    "description": "Distance between polyline points in km",
-    "minimum": 1,
-    "type": "number"
-  }
-}
    • addedInput schema / properties / route_options / title
      Added value: +"Route Options"
    • removedInput schema / properties / route_options / type
      Removed value: -"object"
    • changedInput schema / required
      Previous value: -[
-  "departure",
-  "arrival",
-  "aircraft"
-]New value: +[
+  "departure",
+  "arrival"
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "result": {
+      "title": "Result",
+      "type": "string"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "_WrappedResult",
+  "type": "object",
+  "x-fastmcp-wrap-result": true
+}
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden. It explains that errors are caught internally and returned as strings, and it outlines the return structure. This provides good insight into the tool's behavior.

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 well-structured with 'Args', 'Returns', and 'Raises' sections. Every sentence adds value, and there is no redundancy. It is appropriately sized for the tool's complexity.

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 the output schema exists (implied by the detailed return description), the description adequately covers return values. It also mentions error handling. However, it lacks information about prerequisites or required permissions, but these are not critical for this tool.

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 schema has 0% description coverage, but the description adds meaning by specifying that 'departure' and 'arrival' are dicts with 'city', 'country', 'iata', and that 'aircraft' includes 'ac_type', 'cruise_alt_ft', 'route_step_km'. This significantly compensates for the schema's lack of detail.

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 'Plan a flight route between two airports with performance estimates', which is a specific verb+resource combination. This clearly distinguishes it from sibling tools like 'calculate_distance' or 'get_aircraft_performance'.

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 usage for flight route planning but does not explicitly state when to use this tool versus alternatives like 'calculate_distance' or 'get_aircraft_performance'. There is no when-not-to-use guidance.

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