Skip to main content
Glama

China Import Quote Preflight

by io.github.yl124915300-dot
OverviewDiscussionsAdmin

Run trade preflight

trade_preflight
Read-only

Use BEFORE accepting or paying a China supplier quote for one China → US or China → EU shipment. This shipment-level gate exposes missing landed-cost inputs, dated low-value rule changes, and compliance blockers for low-regulation physical goods. Use normalize_supplier_quote for one quote, compare_preflight_quotes for 2–5 quotes, and check_trade_requirements for a checklist. Do not use it as a freight-rate marketplace, HTS/TARIC classifier, customs brokerage service, or legal advice. Output includes status, corridor, missing_fields, dated authoritative_sources, estimated_landed_cost_components, de_minimis_low_value_treatment, compliance_flags, human_review_reason, and disclaimer. UNKNOWN means a cost or rule cannot be established from supplied inputs; NEEDS_MORE_DATA means required values are missing; MANUAL_REVIEW means a human importer, broker, or compliance reviewer must decide.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hs_codeNoOptional supplier- or broker-provided HS/HTS/CN code. Omit if not already available; this tool never fabricates or independently validates classification and will request manual review.
incotermNoOptional three-letter Incoterms rule such as EXW, FOB, DAP, or DDP. Supply it when stated on the quote; omit only when unknown and expect a missing-field flag.
quantityYesRequired positive number of physical units; use the supplier quote quantity, not cartons unless each carton is the priced unit.
unit_valueYesRequired non-negative per-unit goods value. Pass a number with unit_value_currency, or an object containing amount/value and currency.
material_useNoOptional material and intended-use context, such as textile consumer gift item. Supply it to improve restricted-category and compliance screening; omit only when genuinely unknown.
shipping_costNoOptional quoted shipping/freight amount for the shipment. Omit when unknown; the output will mark shipping and the all-in total UNKNOWN.
origin_countryYesRequired country where the goods ship from; this v1 accepts China, CN, PRC, or equivalent wording.
destination_countryYesRequired destination country or EU; this v1 supports United States and EU member states only.
product_descriptionYesRequired plain-language description of the physical good; include material and intended use here or in material_use. Do not use for services or restricted goods.
unit_value_currencyNoCurrency for a numeric unit_value. Omit only when unit_value is an object that already carries currency; omitting both leaves the goods subtotal UNKNOWN.
shipping_cost_currencyNoCurrency for a numeric shipping_cost. Omit when shipping_cost is an object carrying currency or when shipping_cost is omitted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed15 schema fields changed
    • addedInput schema / properties / destination_country / description
      Added value: +"Required destination country or EU; this v1 supports United States and EU member states only."
    • addedInput schema / properties / hs_code / description
      Added value: +"Optional supplier- or broker-provided HS/HTS/CN code. Omit if not already available; this tool never fabricates or independently validates classification and will request manual review."
    • addedInput schema / properties / incoterm / description
      Added value: +"Optional three-letter Incoterms rule such as EXW, FOB, DAP, or DDP. Supply it when stated on the quote; omit only when unknown and expect a missing-field flag."
    • addedInput schema / properties / material_use / description
      Added value: +"Optional material and intended-use context, such as textile consumer gift item. Supply it to improve restricted-category and compliance screening; omit only when genuinely unknown."
    • addedInput schema / properties / origin_country / description
      Added value: +"Required country where the goods ship from; this v1 accepts China, CN, PRC, or equivalent wording."
    • addedInput schema / properties / product_description / description
      Added value: +"Required plain-language description of the physical good; include material and intended use here or in material_use. Do not use for services or restricted goods."
    • addedInput schema / properties / quantity / description
      Added value: +"Required positive number of physical units; use the supplier quote quantity, not cartons unless each carton is the priced unit."
    • addedInput schema / properties / shipping_cost / description
      Added value: +"Optional quoted shipping/freight amount for the shipment. Omit when unknown; the output will mark shipping and the all-in total UNKNOWN."
    • addedInput schema / properties / shipping_cost / oneOf
      Added value: +[
+  {
+    "minimum": 0,
+    "type": "number"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "amount": {
+        "description": "Non-negative amount in the stated currency.",
+        "minimum": 0,
+        "type": "number"
+      },
+      "currency": {
+        "description": "Three-letter ISO 4217 currency code, for example USD or EUR.",
+        "pattern": "^[A-Za-z]{3}$",
+        "type": "string"
+      },
+      "value": {
+        "description": "Alias for amount; use amount when possible.",
+        "minimum": 0,
+        "type": "number"
+      }
+    },
+    "type": "object"
+  }
+]
    • addedInput schema / properties / shipping_cost_currency / description
      Added value: +"Currency for a numeric shipping_cost. Omit when shipping_cost is an object carrying currency or when shipping_cost is omitted."
    • addedInput schema / properties / shipping_cost_currency / pattern
      Added value: +"^[A-Za-z]{3}$"
    • addedInput schema / properties / unit_value / description
      Added value: +"Required non-negative per-unit goods value. Pass a number with unit_value_currency, or an object containing amount/value and currency."
    • addedInput schema / properties / unit_value / oneOf
      Added value: +[
+  {
+    "minimum": 0,
+    "type": "number"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "amount": {
+        "description": "Non-negative amount in the stated currency.",
+        "minimum": 0,
+        "type": "number"
+      },
+      "currency": {
+        "description": "Three-letter ISO 4217 currency code, for example USD or EUR.",
+        "pattern": "^[A-Za-z]{3}$",
+        "type": "string"
+      },
+      "value": {
+        "description": "Alias for amount; use amount when possible.",
+        "minimum": 0,
+        "type": "number"
+      }
+    },
+    "type": "object"
+  }
+]
    • addedInput schema / properties / unit_value_currency / description
      Added value: +"Currency for a numeric unit_value. Omit only when unit_value is an object that already carries currency; omitting both leaves the goods subtotal UNKNOWN."
    • addedInput schema / properties / unit_value_currency / pattern
      Added value: +"^[A-Za-z]{3}$"
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already indicate readOnlyHint=true and destructiveHint=false, and the description adds substantial behavioral context: it never fabricates or independently validates classification, it flags missing values, and it returns statuses such as UNKNOWN, NEEDS_MORE_DATA, and MANUAL_REVIEW with definitions. It also discloses version limits (v1 supports only China origin, US/EU destination). 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is long but dense and well-structured: usage context, sibling routing, exclusions, output field list, and status definitions each earn their place. Critical usage guidance is front-loaded, and there is no filler or redundancy.

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?

With no output schema, the description compensates by enumerating output fields and explaining status values. It covers the tool's domain limits, data requirements, and safety posture, making it complete enough for an agent to invoke correctly without additional external knowledge.

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% with detailed parameter descriptions, so the baseline is 3; the description adds meaningful semantic guidance beyond the schema by explaining how omitted shipping_cost leads to UNKNOWN components, how hs_code omission triggers manual review, and what the status values mean. It stops short of fully elaborating every parameter interaction, but the additions are valuable.

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 a highly specific verb and resource: 'Run trade preflight' for one China → US/EU shipment gate before accepting/paying a supplier quote. It distinguishes itself clearly from siblings by naming normalize_supplier_quote, compare_preflight_quotes, and check_trade_requirements and their conditions.

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 explicitly says 'Use BEFORE accepting or paying', names the sibling tools and when they apply ('normalize_supplier_quote for one quote, compare_preflight_quotes for 2–5 quotes, check_trade_requirements for a checklist'), and gives explicit negative guidance: 'Do not use it as a freight-rate marketplace, HTS/TARIC classifier, customs brokerage service, or legal advice.'

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

All China Import Quote Preflight toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources