Skip to main content
Glama

China Import Quote Preflight

by io.github.yl124915300-dot
OverviewDiscussionsAdmin

Server Details

Before-payment check for China quotes to US/EU: costs, low-value rules, and compliance blockers.

Ownership verified
Status
Healthy
Uptime
99.9% over 21 days
Last Tested
Transport
Streamable HTTP · MCP 2025-06-18
URL

TDQS

A4.6/5.0

Scored across 4 tools

Disambiguation4/5

The tools are mostly distinct and explicitly cross-reference each other by workflow stage. check_trade_requirements and trade_preflight have some overlap as both surface compliance requirements, but their phase distinction (pre-quote checklist vs shipment-level gate) makes misselection unlikely.

Naming Consistency4/5

Three tools follow a clear verb_object snake_case pattern: check_trade_requirements, compare_preflight_quotes, and normalize_supplier_quote. trade_preflight breaks the pattern as a noun phrase, but the names remain readable and predictable overall.

Tool Count5/5

Four tools is well-scoped for the narrow purpose of China import quote preflight. Each tool maps to a distinct stage of the workflow: requirements checklist, quote normalization, quote comparison, and shipment-level preflight.

Completeness5/5

The set covers the full intended workflow with no dead ends: check requirements, normalize one quote, compare multiple quotes, and run a shipment-level gate. It deliberately excludes adjacent domains like tariff classification and brokerage, which are appropriately disclaimed rather than missing.

Available Tools

4 tools
check_trade_requirementsCheck trade requirements before quote/paymentA
Read-only
Inspect

Use BEFORE asking a China supplier for a final quote or before paying, when you need the minimum data/compliance checklist for China → US or China → EU low-regulation physical goods. Use normalize_supplier_quote when you already have one quote, compare_preflight_quotes for 2–5 quotes, and trade_preflight for shipment-level cost/rule screening. Do not use it as a tariff classifier, freight marketplace, customs broker, or legal adviser. Output includes required_fields, recommended_fields, manual_review_flags, product_risk_flags, authoritative_sources, and status. UNKNOWN means the corridor or a requirement cannot be established; NEEDS_MORE_DATA means more inputs are needed; MANUAL_REVIEW means a human must review the product or entry.

ParametersJSON Schema
NameRequiredDescriptionDefault
material_useNoOptional material and intended use, such as textile or consumer gift item. Supply when known to improve risk screening.
origin_countryYesRequired origin country; use China/CN/PRC for this v1 corridor.
destination_countryYesRequired destination country or EU; use United States or an EU member state.
product_descriptionNoOptional plain-language physical-good description. Omit only if unknown; product-specific requirements then remain incomplete.

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, which the description doesn't contradict. The description adds behavioral context by enumerating the output fields (required_fields, recommended_fields, etc.) and explaining the status semantics (UNKNOWN, NEEDS_MORE_DATA, MANUAL_REVIEW), which is useful beyond the 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?

Four sentences convey usage timing, sibling alternatives, exclusions, output fields, and status meanings without redundancy. Key usage guidance is front-loaded, and every sentence earns its place.

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?

For a read-only checklist tool with full schema coverage, the description is complete: it lists output fields, explains status values, defines scope (specific corridors), and gives explicit boundaries. An agent has all information needed to invoke it 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 description coverage is 100%, so all four parameters are fully documented in the input schema. The description does not add parameter-specific details beyond what the schema provides (e.g., it doesn't mention material_use or product_description), so it stays at the baseline 3 for high schema coverage.

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 specific verb+resource: it checks the minimum data/compliance checklist for China→US or China→EU goods before quote/payment. It explicitly distinguishes itself from siblings by naming normalize_supplier_quote, compare_preflight_quotes, and trade_preflight and their respective use cases, making selection unambiguous.

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 states when to use ('BEFORE asking for a final quote or before paying') and lists negative use cases ('Do not use it as a tariff classifier, freight marketplace, customs broker, or legal adviser'). It also names alternatives with clear conditions, leaving nothing to inference.

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

compare_preflight_quotesCompare 2–5 supplier quotesA
Read-only
Inspect

Use BEFORE choosing or paying a supplier to compare 2–5 China supplier quotes for the same China → US or China → EU purchase. Each item may be a raw quote accepted by normalize_supplier_quote or an existing preflight_quote_passport. Use normalize_supplier_quote first when you have only one quote, and trade_preflight for a shipment-level gate. Do not use it as a freight-rate marketplace, tariff classifier, customs brokerage service, or legal advice. Output includes comparable, comparison_basis, rows, ranking, excluded_from_comparison, and message. UNKNOWN means goods-plus-shipping cannot be computed; NEEDS_MORE_DATA means inputs are incomplete; MANUAL_REVIEW means a human must resolve a product/compliance flag. A ranking is never an all-in landed-cost winner.

ParametersJSON Schema
NameRequiredDescriptionDefault
quotesYesRequired array of 2–5 raw supplier quote objects or preflight_quote_passport outputs. Keep corridor, currency, quantity, unit price, and shipping fields comparable; missing or mixed values are reported rather than guessed.

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true. The description adds meaningful context: output fields (comparable, comparison_basis, rows, ranking, excluded_from_comparison, message), status meanings (UNKNOWN, NEEDS_MORE_DATA, MANUAL_REVIEW), and the caveat that a ranking is never an all-in landed-cost winner. 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?

Seven sentences, front-loaded with primary use case and sibling routing, then exclusions, output fields, status meanings, and a critical caveat. No filler; every sentence carries operational value.

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?

Complex comparison tool with no output schema, but the description compensates by enumerating output fields and status semantics, naming siblings, and giving explicit non-goals. The single parameter is thoroughly documented.

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 value by clarifying each item may be a raw quote accepted by normalize_supplier_quote or an existing preflight_quote_passport, and the schema's own guidance on comparability reinforces correct usage.

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?

States a specific verb and resource: 'compare 2–5 China supplier quotes' for a defined corridor and purchase stage. It explicitly distinguishes itself from siblings by saying when to use normalize_supplier_quote and trade_preflight instead.

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 says 'Use BEFORE choosing or paying a supplier', tells you to use normalize_supplier_quote for a single quote and trade_preflight for a shipment-level gate, and lists forbidden use-cases (freight marketplace, tariff classifier, customs brokerage, legal advice).

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

normalize_supplier_quoteNormalize supplier quote before paymentA
Read-only
Inspect

Use BEFORE accepting or paying one China supplier quote. Turn the quote into a comparable preflight_quote_passport, preserve Incoterm and validity context, and expose missing landed-cost fields and hidden/unknown costs. Use compare_preflight_quotes for 2–5 quotes and trade_preflight for a shipment-level gate. Do not use it as a live freight quote, HTS/TARIC classifier, customs brokerage service, or legal advice. Output includes quote, preflight, missing_quote_fields, hidden_or_unknown_costs, ready_for_comparison, and disclaimer. UNKNOWN means a cost or field is not supplied; NEEDS_MORE_DATA means the passport cannot support a reliable comparison; MANUAL_REVIEW means a human must decide.

ParametersJSON Schema
NameRequiredDescriptionDefault
hs_codeNoOptional supplier- or broker-provided HS/HTS/CN code. Omit if unavailable; no classification is fabricated.
currencyNoCurrency for a numeric unit_price. Omit only when unit_price is an object carrying currency; otherwise the passport marks currency missing.
incotermNoOptional stated Incoterms rule, for example EXW, FOB, DAP, or DDP. Omit only when absent from the quote; it will be listed as missing.
quantityYesRequired positive number of units covered by the supplier quote.
lead_timeNoOptional supplier production/transit lead-time text, such as 15 days. Omit when not stated.
unit_priceYesRequired non-negative per-unit supplier price. Pass a number with currency, or an object containing amount/value and currency.
material_useNoOptional material and intended-use context. Supply it when known to improve restricted-category screening.
shipping_costNoOptional quoted freight/shipping amount. Omit when the supplier did not state it; hidden_or_unknown_costs will flag the gap.
origin_countryYesRequired country of shipment origin; this v1 is for China/CN/PRC.
quote_valid_untilNoOptional supplier validity date or text, preferably YYYY-MM-DD. Omit when the quote has no stated expiry.
shipping_currencyNoCurrency for a numeric shipping_cost. Omit when shipping_cost is an object carrying currency or is absent.
destination_countryYesRequired destination country or EU; this v1 supports United States and EU member states.
product_descriptionNoOptional plain-language physical-good description; strongly recommended before payment and needed for a useful product-risk screen.

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds meaningful behavioral context beyond annotations by defining the transformation into a preflight_quote_passport, enumerating output fields, and explaining the semantics of UNKNOWN, NEEDS_MORE_DATA, and MANUAL_REVIEW. No contradiction with annotations exists.

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 front-loaded with the most critical usage instruction ('Use BEFORE accepting or paying') and every sentence earns its place: purpose, alternative tools, exclusions, output fields, and status definitions. It is compact despite covering a complex tool.

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?

For a 13-parameter tool with no output schema, the description is remarkably complete: it states scope, alternatives, non-uses, outputs, and status vocabulary. Combined with the fully documented schema and annotations, an agent has everything needed to select and invoke the tool correctly.

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 input schema already documents every parameter and its role. The description reinforces high-level concepts like Incoterm preservation, validity context, and hidden costs, but it does not add parameter-level detail beyond what the schema provides; baseline 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 uses a specific verb and resource: normalize a single supplier quote into a comparable preflight_quote_passport. It clearly distinguishes this tool from siblings by framing it around one quote before payment, while compare_preflight_quotes and trade_preflight are explicitly named as different operations.

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?

Explicit timing is given ('BEFORE accepting or paying one China supplier quote'), plus direct routing to alternatives: compare_preflight_quotes for 2–5 quotes and trade_preflight for shipment-level gates. It also lists exclusions such as live freight quote, HTS/TARIC classifier, customs brokerage, and legal advice, leaving no ambiguity about when to use it.

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

trade_preflightRun trade preflightA
Read-only
Inspect

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.

ParametersJSON 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.

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.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 4 tool updates
    • Changedcheck_trade_requirements4 fields changed
      • addedInput schema / properties / destination_country / description
        Added value: +"Required destination country or EU; use United States or an EU member state."
      • addedInput schema / properties / material_use / description
        Added value: +"Optional material and intended use, such as textile or consumer gift item. Supply when known to improve risk screening."
      • addedInput schema / properties / origin_country / description
        Added value: +"Required origin country; use China/CN/PRC for this v1 corridor."
      • addedInput schema / properties / product_description / description
        Added value: +"Optional plain-language physical-good description. Omit only if unknown; product-specific requirements then remain incomplete."
    • Changedcompare_preflight_quotes2 fields changed
      • addedInput schema / properties / quotes / description
        Added value: +"Required array of 2–5 raw supplier quote objects or preflight_quote_passport outputs. Keep corridor, currency, quantity, unit price, and shipping fields comparable; missing or mixed values are reported rather than guessed."
      • addedInput schema / properties / quotes / items / description
        Added value: +"One raw supplier quote with normalize_supplier_quote fields, or one preflight_quote_passport returned by that tool."
    • Changednormalize_supplier_quote17 fields changed
      • addedInput schema / properties / currency / description
        Added value: +"Currency for a numeric unit_price. Omit only when unit_price is an object carrying currency; otherwise the passport marks currency missing."
      • addedInput schema / properties / currency / pattern
        Added value: +"^[A-Za-z]{3}$"
      • addedInput schema / properties / destination_country / description
        Added value: +"Required destination country or EU; this v1 supports United States and EU member states."
      • addedInput schema / properties / hs_code / description
        Added value: +"Optional supplier- or broker-provided HS/HTS/CN code. Omit if unavailable; no classification is fabricated."
      • addedInput schema / properties / incoterm / description
        Added value: +"Optional stated Incoterms rule, for example EXW, FOB, DAP, or DDP. Omit only when absent from the quote; it will be listed as missing."
      • addedInput schema / properties / lead_time / description
        Added value: +"Optional supplier production/transit lead-time text, such as 15 days. Omit when not stated."
      • addedInput schema / properties / material_use / description
        Added value: +"Optional material and intended-use context. Supply it when known to improve restricted-category screening."
      • addedInput schema / properties / origin_country / description
        Added value: +"Required country of shipment origin; this v1 is for China/CN/PRC."
      • addedInput schema / properties / product_description / description
        Added value: +"Optional plain-language physical-good description; strongly recommended before payment and needed for a useful product-risk screen."
      • addedInput schema / properties / quantity / description
        Added value: +"Required positive number of units covered by the supplier quote."
      • addedInput schema / properties / quote_valid_until / description
        Added value: +"Optional supplier validity date or text, preferably YYYY-MM-DD. Omit when the quote has no stated expiry."
      • addedInput schema / properties / shipping_cost / description
        Added value: +"Optional quoted freight/shipping amount. Omit when the supplier did not state it; hidden_or_unknown_costs will flag the gap."
      • 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_currency / description
        Added value: +"Currency for a numeric shipping_cost. Omit when shipping_cost is an object carrying currency or is absent."
      • addedInput schema / properties / shipping_currency / pattern
        Added value: +"^[A-Za-z]{3}$"
      • addedInput schema / properties / unit_price / description
        Added value: +"Required non-negative per-unit supplier price. Pass a number with currency, or an object containing amount/value and currency."
      • addedInput schema / properties / unit_price / 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"
+  }
+]
    • Changedtrade_preflight15 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. 4 tool updates
    • First observedcheck_trade_requirements
    • First observedcompare_preflight_quotes
    • First observednormalize_supplier_quote
    • First observedtrade_preflight

Related MCP Connectors

Related MCP Servers

  • Jikgu Customs MCP

    elinysh
    F
    license
    Not graded
    quality
    D
    maintenance
    Calculates estimated import duties, taxes, and customs clearance rules for overseas purchases, with all tools being read-only and operating without external API calls.
    -

  • HS Code MCP Server

    dcd887
    A
    license
    Not graded
    quality
    C
    maintenance
    Enables AI agents to search Chinese HS commodity codes, retrieve detailed tariff and regulatory information, and calculate import taxes using 2026 import/export tariff data.
    MIT

  • wanhe-compliance

    Wh-bi
    A
    license
    Not graded
    quality
    B
    maintenance
    Enables AI agents to check Chinese commercial content for advertising-law prohibited terms, AI-generated-content labeling requirements, and 17-item organizational compliance self-assessment, returning each hit with its location, cited legal basis, and revision suggestion. Runs fully offline with a deterministic rule engine and zero external dependencies.
    MIT
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