Skip to main content
Glama

FreightUtils MCP Server

by io.github.SoapyRED

Freight Identifier Validator

validate
Read-onlyIdempotent

Validate and parse freight identifiers by their public check-digit algorithms: shipping container numbers (ISO 6346), air waybill (AWB) numbers (IATA modulus-7) and IMO ship identification numbers.

Two modes: pass text= to find and validate every identifier in it (e.g. a booking-email line), OR pass value= + type=<container|awb|imo> to validate one.

Behavior: deterministic check-digit arithmetic; per identifier found it reports type, the normalised form, valid (pass/fail), expected vs actual check digit, and details (container: owner prefix + equipment category; AWB: airline prefix + the operating airline resolved from the AWB-prefix dataset; IMO: the 7-digit number); text mode with no identifiers found returns an empty found[] with a note. 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: found[] (each entry with its own _source naming the standard applied) and disclaimer under result, plus confidence, _source and citation (the FreightUtils v1 response envelope).

Limitations: STRUCTURAL ONLY — a valid check digit means well-formed, NOT that the container, shipment or vessel exists or is active; not a registry or tracking lookup.

Related: container_lookup (container TYPE specs, not numbers), airline_lookup (the AWB-prefix dataset the airline resolution uses).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textNoArbitrary string to scan for container / AWB / IMO identifiers (parse mode). Provide this OR value+type.
typeNoIdentifier type for value: container = ISO 6346, awb = IATA Air Waybill, imo = IMO ship number.
valueNoA single identifier to validate (typed mode). Requires type.

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. Changed14 schema fields changed
    • addedOutput schema / properties / _source
      Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "checked": {
+      "type": "string"
+    },
+    "name": {
+      "type": "string"
+    },
+    "provenance_status": {
+      "enum": [
+        "verified",
+        "pending-verification",
+        "computed",
+        "live"
+      ],
+      "type": "string"
+    },
+    "source_url": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "name",
+    "checked",
+    "provenance_status"
+  ],
+  "type": "object"
+}
    • 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 / disclaimer
      Removed value: -{
-  "description": "Structural-validation-only disclaimer",
-  "type": "string"
-}
    • addedOutput schema / properties / envelope_version
      Added value: +{
+  "const": "1",
+  "type": "string"
+}
    • removedOutput schema / properties / found
      Removed value: -{
-  "description": "Every identifier found + validated (ordered by position in the input)",
-  "items": {
-    "additionalProperties": false,
-    "properties": {
-      "_source": {
-        "additionalProperties": false,
-        "description": "Methodology citation for the scheme",
-        "properties": {
-          "authority": {
-            "type": "string"
-          },
-          "computed_by": {
-            "type": "string"
-          },
-          "reference": {
-            "type": "string"
-          },
-          "source_url": {
-            "type": "string"
-          },
-          "standard": {
-            "type": "string"
-          },
-          "type": {
-            "type": "string"
-          }
-        },
-        "required": [
-          "type",
-          "standard",
-          "reference",
-          "authority",
-          "source_url",
-          "computed_by"
-        ],
-        "type": "object"
-      },
-      "check_digit": {
-        "additionalProperties": false,
-        "description": "Expected vs actual check digit (null if malformed)",
-        "properties": {
-          "actual": {
-            "anyOf": [
-              {
-                "type": "number"
-              },
-              {
-                "type": "null"
-              }
-            ]
-          },
-          "expected": {
-            "anyOf": [
-              {
-                "type": "number"
-              },
-              {
-                "type": "null"
-              }
-            ]
-          }
-        },
-        "required": [
-          "expected",
-          "actual"
-        ],
-        "type": "object"
-      },
-      "details": {
-        "additionalProperties": {},
-        "description": "Type-specific: owner_prefix/equipment_category (container), airline_prefix/serial/airline (awb), number (imo), or error (malformed)",
-        "propertyNames": {
-          "type": "string"
-        },
-        "type": "object"
-      },
-      "normalised": {
-        "description": "Canonical form (uppercased / dashed)",
-        "type": "string"
-      },
-      "raw": {
-        "description": "The candidate as found in the input",
-        "type": "string"
-      },
-      "type": {
-        "description": "container | awb | imo",
-        "type": "string"
-      },
-      "valid": {
-        "description": "Check-digit pass/fail (structural only)",
-        "type": "boolean"
-      }
-    },
-    "required": [
-      "type",
-      "raw",
-      "normalised",
-      "valid",
-      "check_digit",
-      "details",
-      "_source"
-    ],
-    "type": "object"
-  },
-  "type": "array"
-}
    • addedOutput schema / properties / normalized_input
      Added value: +{
+  "additionalProperties": {},
+  "propertyNames": {
+    "type": "string"
+  },
+  "type": "object"
+}
    • removedOutput schema / properties / note
      Removed value: -{
-  "description": "Present when nothing was found",
-  "type": "string"
-}
    • addedOutput schema / properties / ok
      Added value: +{
+  "type": "boolean"
+}
    • addedOutput schema / properties / result
      Added value: +{
+  "additionalProperties": {},
+  "propertyNames": {
+    "type": "string"
+  },
+  "type": "object"
+}
    • 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: -[
-  "found",
-  "disclaimer"
-]New value: +[
+  "envelope_version",
+  "ok",
+  "result",
+  "confidence",
+  "_source",
+  "citation"
+]
  3. Added

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already indicate readOnly/idempotent, so the bar is lower, but the description adds substantial behavioral context: deterministic arithmetic, per-identifier output fields, rate limits (25 req/day) with retry_after_seconds and Retry-After header, empty found[] behavior, and the structural-only limitation. This goes well beyond the annotation safety profile without contradiction.

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?

Organized into labeled sections (modes, behavior, returns, limitations, related) that move from purpose to operational detail. Every sentence contributes essential content—rate limits, output envelope, structural caveat, alternatives—without redundancy. The length is justified by the tool's complexity.

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?

Covers all materially relevant aspects: the two input modes, per-type validation details, output structure, error/rate-limit handling, limitations, and related tools. An output schema exists but the description still adds contextual value, making the tool fully understandable without external documentation.

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 baseline is 3. The description adds meaningful mode-level semantics: text is for parse mode, value+type is for single validation, and the type enum maps to specific standards. This clarifies the mutual relationship between parameters that the schema does not express, justifying a small increment above baseline.

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+resource: 'Validate and parse freight identifiers by their public check-digit algorithms', naming the three identifier types. It distinguishes itself from siblings in the Related section, explicitly calling out container_lookup and airline_lookup as different in scope.

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?

It gives explicit when-to-use guidance with two modes (text for scanning arbitrary strings, value+type for single validation). It names alternatives (container_lookup, airline_lookup) and excludes registry/tracking use via 'STRUCTURAL ONLY'. Rate-limit handling instructions (back off/retry or get_subscribe_link) are also actionable.

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