Skip to main content
Glama

FreightUtils MCP Server

by io.github.SoapyRED

Nearest Airport

nearest_airport
Read-onlyIdempotent

Find the airports nearest to a caller-provided latitude/longitude, sorted by great-circle (haversine) distance with distance_km on each result. Searches 85,555 airports (OurAirports, public domain).

Provide latitude and longitude (decimal degrees); optional radius_km, max_results (1-50, default 10) and type filter (e.g. large_airport only). Coordinates are INPUT only — nothing is stored or logged.

Behavior: deterministic distance sort; confidence reflects proximity and airport size (a large airport within 25 km scores high; closed/heliport/seaplane results cap lower). This tool does NOT geocode place names and does NOT compute routes — pass coordinates you already hold. Rate-limited (anonymous use: 25 requests/day per IP): a 429 error body carries retry_after_seconds and a Retry-After header — back off and retry, or call get_subscribe_link for higher limits.

Returns: count and results[] (the airport record plus distance_km) under result, plus confidence, _source and citation (the FreightUtils v1 response envelope).

Limitations: reference data only — not for navigation; verify codes with IATA / ICAO.

Related: airport_lookup (exact code or name lookup, no distance), unlocode_lookup (named transport-location search).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoOptional filter by airport type
latitudeYesLatitude in decimal degrees (-90 to 90)
longitudeYesLongitude in decimal degrees (-180 to 180)
radius_kmNoOptional maximum distance in kilometres
max_resultsNoMax results to return (1–50, default 10)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYes
resultYes
_sourceYes
citationYes
validityNo
warningsNo
confidenceYes
blocking_errorsNo
envelope_versionYes
normalized_inputNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed5 schema fields changed
    • addedOutput schema / properties / _source / properties / authority_current_edition
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / properties / _source / properties / checked_at
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / properties / _source / properties / dataset_edition
      Added value: +{
+  "type": "string"
+}
    • removedOutput schema / properties / envelope_version / const
      Removed value: -"1"
    • addedOutput schema / properties / envelope_version / enum
      Added value: +[
+  "1",
+  "1.1"
+]
  2. Changed18 schema fields changed
    • changedOutput schema / properties / _source / additionalProperties
      Previous value: -{
-  "type": "string"
-}New value: +false
    • removedOutput schema / properties / _source / description
      Removed value: -"Provenance envelope (OurAirports, cross-checked)"
    • addedOutput schema / properties / _source / properties
      Added value: +{
+  "checked": {
+    "type": "string"
+  },
+  "name": {
+    "type": "string"
+  },
+  "provenance_status": {
+    "enum": [
+      "verified",
+      "pending-verification",
+      "computed",
+      "live"
+    ],
+    "type": "string"
+  },
+  "source_url": {
+    "type": "string"
+  }
+}
    • removedOutput schema / properties / _source / propertyNames
      Removed value: -{
-  "type": "string"
-}
    • addedOutput schema / properties / _source / required
      Added value: +[
+  "name",
+  "checked",
+  "provenance_status"
+]
    • addedOutput schema / properties / blocking_errors
      Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "code": {
+        "type": "string"
+      },
+      "message": {
+        "type": "string"
+      },
+      "recovery": {
+        "additionalProperties": false,
+        "properties": {
+          "action": {
+            "type": "string"
+          },
+          "params": {
+            "additionalProperties": {},
+            "propertyNames": {
+              "type": "string"
+            },
+            "type": "object"
+          },
+          "tool": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "action"
+        ],
+        "type": "object"
+      }
+    },
+    "required": [
+      "code",
+      "message",
+      "recovery"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
    • addedOutput schema / properties / citation
      Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "qualifier": {
+      "type": "string"
+    },
+    "text": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "text"
+  ],
+  "type": "object"
+}
    • addedOutput schema / properties / confidence
      Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "basis": {
+      "enum": [
+        "deterministic",
+        "provenance",
+        "match_quality",
+        "freshness"
+      ],
+      "type": "string"
+    },
+    "level": {
+      "enum": [
+        "high",
+        "medium",
+        "low"
+      ],
+      "type": "string"
+    },
+    "score": {
+      "maximum": 1,
+      "minimum": 0,
+      "type": "number"
+    }
+  },
+  "required": [
+    "level",
+    "basis"
+  ],
+  "type": "object"
+}
    • removedOutput schema / properties / count
      Removed value: -{
-  "type": "number"
-}
    • removedOutput schema / properties / disclaimer
      Removed value: -{
-  "type": "string"
-}
    • addedOutput schema / properties / envelope_version
      Added value: +{
+  "const": "1",
+  "type": "string"
+}
    • addedOutput schema / properties / normalized_input
      Added value: +{
+  "additionalProperties": {},
+  "propertyNames": {
+    "type": "string"
+  },
+  "type": "object"
+}
    • addedOutput schema / properties / ok
      Added value: +{
+  "type": "boolean"
+}
    • addedOutput schema / properties / result
      Added value: +{
+  "additionalProperties": {},
+  "propertyNames": {
+    "type": "string"
+  },
+  "type": "object"
+}
    • removedOutput schema / properties / results
      Removed value: -{
-  "description": "Nearest airports, ascending by distance_km",
-  "items": {
-    "additionalProperties": false,
-    "properties": {
-      "country": {
-        "description": "ISO 3166-1 alpha-2 country code",
-        "type": "string"
-      },
-      "country_name": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "distance_km": {
-        "description": "Great-circle distance from the query point, km",
-        "type": "number"
-      },
-      "elevation_ft": {
-        "anyOf": [
-          {
-            "type": "number"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "iata_code": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "description": "IATA 3-letter code (null if none)"
-      },
-      "ident": {
-        "description": "ICAO / OurAirports ident",
-        "type": "string"
-      },
-      "latitude": {
-        "type": "number"
-      },
-      "longitude": {
-        "type": "number"
-      },
-      "municipality": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "name": {
-        "type": "string"
-      },
-      "region": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "description": "Region / subdivision (readable)"
-      },
-      "type": {
-        "description": "large_airport | medium_airport | small_airport | heliport | closed | seaplane_base",
-        "type": "string"
-      }
-    },
-    "required": [
-      "ident",
-      "iata_code",
-      "name",
-      "type",
-      "municipality",
-      "region",
-      "country",
-      "country_name",
-      "latitude",
-      "longitude",
-      "elevation_ft",
-      "distance_km"
-    ],
-    "type": "object"
-  },
-  "type": "array"
-}
    • addedOutput schema / properties / validity
      Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "as_of": {
+      "type": "string"
+    },
+    "effective_from": {
+      "type": "string"
+    },
+    "effective_to": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    }
+  },
+  "required": [
+    "as_of"
+  ],
+  "type": "object"
+}
    • addedOutput schema / properties / warnings
      Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "code": {
+        "type": "string"
+      },
+      "details": {
+        "additionalProperties": {},
+        "propertyNames": {
+          "type": "string"
+        },
+        "type": "object"
+      },
+      "message": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "code",
+      "message"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
    • changedOutput schema / required
      Previous value: -[
-  "count",
-  "results",
-  "disclaimer",
-  "_source"
-]New value: +[
+  "envelope_version",
+  "ok",
+  "result",
+  "confidence",
+  "_source",
+  "citation"
+]
  3. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, and non-destructive. The description adds substantial behavioral context: 'Coordinates are INPUT only — nothing is stored or logged,' 'deterministic distance sort,' the confidence scoring rule ('large airport within 25 km scores high; closed/heliport/seaplane results cap lower'), and the 429 retry behavior. These are non-obvious traits not derivable from annotations or schema.

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 organized into clear, purposeful sections: summary, input instructions, behavior, return envelope, limitations, and related tools. Each sentence contributes unique information (e.g., data source, rate limiting, navigation disclaimer). While longer than average, no redundant or filler content exists, and the most critical info (what it does and how to use) is front-loaded.

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 complexity (rate limits, confidence scoring, output envelope) and the presence of an output schema, the description is remarkably complete. It explains the return structure ('count and results[] ... under result, plus confidence, _source and citation'), the confidence semantics, rate-limit handling with retry headers, and the reference-data limitation. This exceeds what schema and annotations alone provide.

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 the baseline is 3. The description adds only marginal parameter context beyond the schema: it reiterates latitude/longitude format, lists optional parameters (radius_km, max_results, type), and gives an example value for type ('e.g. large_airport only'). It does not provide new semantics like edge-case warnings or format specifics not already in the schema.

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 action: 'Find the airports nearest to a caller-provided latitude/longitude, sorted by great-circle (haversine) distance with distance_km on each result.' This clearly identifies the resource (airports) and the unique value (proximity sorted by distance). It also distinguishes itself from sibling tools via the 'Related' section, naming airport_lookup as exact code/name lookup with no distance, and unlocode_lookup as named transport-location search.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly states when to use the tool ('pass coordinates you already hold'), when not to use it ('does NOT geocode place names and does NOT compute routes'), and names alternatives ('Related: airport_lookup... unlocode_lookup...'). It also provides practical guidance on rate limits: 'back off and retry, or call get_subscribe_link for higher limits.' This goes beyond implied usage.

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

All FreightUtils MCP Server toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0
Disambiguation3/5

The tools cluster into clear domains and the descriptions are detailed, but there are several overlapping pairs: consignment_calculator vs shipment_summary, cbm_calculator vs unit_converter, and validate vs resolve_reference all have fuzzy boundaries. An agent could plausibly mis-select between the composite calculators or between identifier-handling tools despite the helpful cross-references.

Naming Consistency4/5

Naming is mostly consistent: reference tools use *_lookup, calculation tools use *_calculator, and checks use *_check. Exceptions like validate, resolve_reference, nearest_airport, and shipment_summary break the dominant pattern slightly, but all names are snake_case and generally predictable.

Tool Count3/5

At 25 tools, this sits at the heavy end of the range for an MCP server. The broad freight/logistics scope justifies many of them, but several single-purpose calculators could have been consolidated or grouped, making the surface feel larger and more redundant than necessary.

Completeness4/5

The server covers ADR dangerous-goods rules, multi-modal freight calculations, equipment lookups, identifier validation, customs/trade data, and emissions estimation. Minor gaps exist—no routing/geocoding, no SCAC/BIC coverage, no customs filing—but core freight-reference and calculation workflows are well supported.

Resources