Skip to main content
Glama
Sign In

Cambridge China Bridge — China sourcing

by uk.co.camchinabridge
OverviewDiscussionsAdmin

Check for anti-dumping duty on Chinese goods

check_anti_dumping
Read-only

Check Chinese goods for trade defence duties. market defaults to uk: uses the live UK Trade Tariff, with no single rate because it depends on the exporter. market eu: searches the sourced EU snapshot by product keyword or CN code prefix and gives indicative ranges and EUR-Lex regulations. Always check TARIC before EU import; no match is not clearance.

Input Schema

NameRequiredDescriptionDefault
localeNoLanguage for names and links: en (default) or zh (Simplified Chinese).
marketNouk
productNoEU only: product keyword in English or Chinese.
commodity_codeNoUK: a 6 to 10 digit commodity code (required). EU: a CN code prefix; alternatively supply product.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / anyOf
      Added value: +[
+  {
+    "required": [
+      "commodity_code"
+    ]
+  },
+  {
+    "properties": {
+      "market": {
+        "const": "eu"
+      }
+    },
+    "required": [
+      "market",
+      "product"
+    ]
+  }
+]
    • changedInput schema / properties / commodity_code / description
      Previous value: -"A 6 to 10 digit UK commodity code."New value: +"UK: a 6 to 10 digit commodity code (required). EU: a CN code prefix; alternatively supply product."
    • addedInput schema / properties / market
      Added value: +{
+  "default": "uk",
+  "enum": [
+    "uk",
+    "eu"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / product
      Added value: +{
+  "description": "EU only: product keyword in English or Chinese.",
+  "type": "string"
+}
    • removedInput schema / required
      Removed value: -[
-  "commodity_code"
-]
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=true, destructiveHint=false). The description adds real behavioral value beyond that: the UK path queries the live Trade Tariff and yields no single rate because it depends on the exporter, while the EU path searches a sourced snapshot and returns indicative ranges and EUR-Lex regulations. The 'no match is not clearance' caveat is an important honesty disclosure, though the exact response shape is not described.

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 dense and front-loaded, leading with the purpose and then the market branches. The telegraphic 'market xyz:' phrasing is efficient, though the compressed style makes the market split slightly harder to parse than plain sentences would.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only, open-world lookup with no output schema, the description covers the key decision points an agent needs: default market, per-market input requirements, per-market data source, and the legal caveat that no match is not clearance. It is largely complete, missing only explicit routing against sibling duty-lookup tools.

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 75%, so most fields carry descriptions, but the description adds meaning the schema does not: it explains the default market, that UK lookups use a 6–10 digit commodity code, and that EU lookup accepts either a product keyword or a CN code prefix. It reinforces the conditional requirement structure rather than simply restating fields.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource ('Check Chinese goods for trade defence duties') and clearly scopes the tool to anti-dumping/countervailing duties rather than general tariff lookup. It does not name the most similar sibling (find_duty_rate), so an agent must infer the boundary between the two from the market-specific behavior described.

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

Usage Guidelines4/5

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

It gives concrete usage context: market defaults to uk, EU requires TARIC verification before import, and it warns 'no match is not clearance.' That is strong when-to-use guidance, but it never states when to prefer a sibling such as find_duty_rate or check_china_import_rules instead.

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

All Cambridge China Bridge — China sourcing 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