Skip to main content
Glama
cheesejaguar

Aerospace MCP

by cheesejaguar
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

calculate_distance

Calculate great circle distance between two coordinates for aviation. Returns distance in km and NM with initial and final bearings.

Instructions

Calculate great circle distance between two points.

Args: lat1: Latitude of first point in degrees lon1: Longitude of first point in degrees lat2: Latitude of second point in degrees lon2: Longitude of second point in degrees

Returns: JSON string with distance in km and NM, plus initial/final bearings.

Raises: No exceptions are raised directly; errors are returned as formatted strings.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
lat1Yes
lon1Yes
lat2Yes
lon2Yes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv1.0.0
    • removedInput schema / properties / destination
      Removed value: -{
-  "properties": {
-    "latitude": {
-      "maximum": 90,
-      "minimum": -90,
-      "type": "number"
-    },
-    "longitude": {
-      "maximum": 180,
-      "minimum": -180,
-      "type": "number"
-    }
-  },
-  "required": [
-    "latitude",
-    "longitude"
-  ],
-  "type": "object"
-}
    • addedInput schema / properties / lat1
      Added value: +{
+  "title": "Lat1",
+  "type": "number"
+}
    • addedInput schema / properties / lat2
      Added value: +{
+  "title": "Lat2",
+  "type": "number"
+}
    • addedInput schema / properties / lon1
      Added value: +{
+  "title": "Lon1",
+  "type": "number"
+}
    • addedInput schema / properties / lon2
      Added value: +{
+  "title": "Lon2",
+  "type": "number"
+}
    • removedInput schema / properties / origin
      Removed value: -{
-  "properties": {
-    "latitude": {
-      "maximum": 90,
-      "minimum": -90,
-      "type": "number"
-    },
-    "longitude": {
-      "maximum": 180,
-      "minimum": -180,
-      "type": "number"
-    }
-  },
-  "required": [
-    "latitude",
-    "longitude"
-  ],
-  "type": "object"
-}
    • removedInput schema / properties / step_km
      Removed value: -{
-  "default": 50,
-  "description": "Step size for polyline generation in km",
-  "minimum": 1,
-  "type": "number"
-}
    • changedInput schema / required
      Previous value: -[
-  "origin",
-  "destination"
-]New value: +[
+  "lat1",
+  "lon1",
+  "lat2",
+  "lon2"
+]
    • 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.1/5.0
Behavior4/5

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

No annotations provided, so description carries full burden. It explains the output format (JSON with km and NM plus bearings) and error handling (returns formatted strings, no exceptions). However, it does not disclose assumptions like Earth radius or formula used.

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?

Description is well-structured with Args, Returns, and Raises sections. Every sentence is informative, no fluff.

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?

Given the tool's simplicity and the presence of an output schema, the description covers purpose, all parameters, return format, and error handling. It is complete for its context.

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 coverage is 0%, so description must add value. The description lists the parameters by name (lat1, lon1, etc.) but adds no additional detail beyond what the schema provides (e.g., valid ranges, units). Baseline of 3 is appropriate.

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 purpose: 'Calculate great circle distance between two points.' It uses a specific verb (calculate) and resource (distance), and distinguishes itself from sibling tools which cover different aerospace calculations.

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?

No explicit guidance on when to use this tool versus alternatives. The description implies it is for great circle distance, but does not state when other distance methods might be preferred.

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