FreightUtils MCP Server

ICS2 Stop-Words Checker

ics2_check

Read-onlyIdempotent

Check a goods description against the official EU ICS2 stop-words list — terms the European Commission deems too vague or generic for an entry summary declaration (ENS) goods-description field (data element 18 05 000 000).

Pass description=. Behavior: deterministic term matching against the in-force EU list; each flagged term carries a note (a standalone stop-word means automatic rejection, an embedded one means make the description more specific); clean=true means no listed term matched — it does NOT guarantee acceptance, and no binary accepted/rejected verdict is given. 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: the description echo, flagged[] (term + note), clean, caveat and disclaimer under result, plus a _source citing the EU list and legal basis, plus confidence, _source and citation (the FreightUtils v1 response envelope).

Limitations: STRICTLY a reference check — not an ENS filing, not a customs-compliance determination, not legal advice; the EU list is non-exhaustive and updated periodically.

Related: hs_code_lookup (commodity codes — a different field of the ENS), uk_duty_calculator (duty/VAT, unrelated to ENS screening). Use BEFORE filing an ENS — for customs/documentation teams, brokers and agents building filing pipelines.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`description`	Yes	The goods description to check against the EU ICS2 stop-words list.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`ok`	Yes
`result`	Yes
`_source`	Yes
`citation`	Yes
`validity`	No
`warnings`	No
`confidence`	Yes
`blocking_errors`	No
`envelope_version`	Yes
`normalized_input`	No

Schema Changelog

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

Changed5 schema fields changedAug 11, 2026
- 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"
+]
```

Changed29 schema fields changedJul 9, 2026

removedOutput schema / properties / _source / description

Removed value: -"Citability envelope: EU ICS2 list + legal basis + provenance"

removedOutput schema / properties / _source / properties / authority
```
Removed value: -{
-  "type": "string"
-}
```
addedOutput schema / properties / _source / properties / checked
```
Added value: +{
+  "type": "string"
+}
```
removedOutput schema / properties / _source / properties / dataset
```
Removed value: -{
-  "type": "string"
-}
```
removedOutput schema / properties / _source / properties / legal_basis
```
Removed value: -{
-  "type": "string"
-}
```
removedOutput schema / properties / _source / properties / licence
```
Removed value: -{
-  "type": "string"
-}
```
removedOutput schema / properties / _source / properties / list_in_force
```
Removed value: -{
-  "type": "string"
-}
```
addedOutput schema / properties / _source / properties / name
```
Added value: +{
+  "type": "string"
+}
```
removedOutput schema / properties / _source / properties / non_exhaustive
```
Removed value: -{
-  "type": "boolean"
-}
```

addedOutput schema / properties / _source / properties / provenance_status

Added value: +{
+  "enum": [
+    "verified",
+    "pending-verification",
+    "computed",
+    "live"
+  ],
+  "type": "string"
+}

removedOutput schema / properties / _source / properties / retrieved
```
Removed value: -{
-  "type": "string"
-}
```
removedOutput schema / properties / _source / properties / retrieved_via
```
Removed value: -{
-  "type": "string"
-}
```
removedOutput schema / properties / _source / properties / type
```
Removed value: -{
-  "type": "string"
-}
```

changedOutput schema / properties / _source / required

Previous value: -[
-  "type",
-  "authority",
-  "dataset",
-  "legal_basis",
-  "list_in_force",
-  "source_url",
-  "licence",
-  "retrieved",
-  "non_exhaustive",
-  "retrieved_via"
-]New 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"
+}

removedOutput schema / properties / caveat

Removed value: -{
-  "description": "Non-exhaustive-list caveat: clean does not mean accepted",
-  "type": "string"
-}

addedOutput schema / properties / citation

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "qualifier": {
+      "type": "string"
+    },
+    "text": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "text"
+  ],
+  "type": "object"
+}

removedOutput schema / properties / clean

Removed value: -{
-  "description": "True if no listed stop-word was found — NOT a guarantee of acceptance",
-  "type": "boolean"
-}

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 / description

Removed value: -{
-  "description": "Echo of the submitted description",
-  "type": "string"
-}

removedOutput schema / properties / disclaimer

Removed value: -{
-  "description": "Reference-only disclaimer",
-  "type": "string"
-}

addedOutput schema / properties / envelope_version

Added value: +{
+  "const": "1",
+  "type": "string"
+}

removedOutput schema / properties / flagged

Removed value: -{
-  "description": "Listed stop-words found (empty if none)",
-  "items": {
-    "additionalProperties": false,
-    "properties": {
-      "note": {
-        "description": "Standalone (automatic rejection) vs embedded guidance",
-        "type": "string"
-      },
-      "term": {
-        "description": "The listed stop-word found",
-        "type": "string"
-      }
-    },
-    "required": [
-      "term",
-      "note"
-    ],
-    "type": "object"
-  },
-  "type": "array"
-}

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"
+}

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: -[
-  "description",
-  "flagged",
-  "clean",
-  "caveat",
-  "_source",
-  "disclaimer"
-]New value: +[
+  "envelope_version",
+  "ok",
+  "result",
+  "confidence",
+  "_source",
+  "citation"
+]

AddedJun 24, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, and the description adds substantial behavioral detail: deterministic term matching, flagged terms with notes, the meaning of clean, no binary verdict, rate limits, 429 error handling with retry_after_seconds, and periodic list updates. No contradiction with 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 long but well-structured: purpose, behavior, return format, limitations, and related tools are separated into clear sections. It is front-loaded with the primary function. Though verbose, each sentence earns its place; only minor redundancy exists in describing the return envelope when output schema is present.

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?

Despite having an output schema, the description thoroughly explains return fields, limitations, rate limits, legal disclaimers, and the non-exhaustive nature of the list. It provides complete context for an agent to invoke the tool correctly and interpret results.

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 100% and the schema description already states 'The goods description to check against the EU ICS2 stop-words list.' The description's 'Pass description=<goods description>' is redundant with the schema. No additional parameter semantics are provided beyond what the schema already offers.

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: 'Check a goods description against the official EU ICS2 stop-words list', clearly scoping the tool to a distinct function. It explicitly differentiates from siblings by naming hs_code_lookup and uk_duty_calculator as covering different fields of ENS screening.

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?

Explicitly states when to use ('Use BEFORE filing an ENS') and what the tool is not for ('not an ENS filing, not a customs-compliance determination, not legal advice'). It also provides alternatives: 'call get_subscribe_link for higher limits' and names hs_code_lookup/uk_duty_calculator for other purposes.

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 tools Inspect

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.

ICS2 Stop-Words Checker

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

TDQS

Resources