Skip to main content
Glama

What exporters miss: blockers, approvals, extra duties

blind_spots
Read-onlyIdempotent

What a Korean exporter of this product is likely to miss in a market — the unknown unknowns beyond the product category's usual compliance: rules that can stop the sale (e.g. UV filters not allowed in US sunscreen, meat ingredients from countries the EU has not listed), approvals needed before import or sale (radio certification such as FCC, EU RED, Japan's Giteki or Canada's ISED; India BIS; registration of special-use cosmetics in China), extra duties or charges that change the quote (US Section 232 on steel and aluminium content, EU CBAM), and filings or labels (EU deforestation due diligence, producer registration (EPR) for batteries and electronics, and packaging EPR such as Germany's LUCID register in packaging_epr, EU ban on generic green claims), plus Korea-side checks (strategic items, dangerous goods in shipping). Each rule is triggered by the exact HS code or a product trait (pass description or traits) and comes with kind, gate (true = clear it before anything else: the plan's before-you-sell gate), who must act (you or the importer), the date it applies from (upcoming rules too), the official source and the date it was checked; stale marks rules not re-checked for 180 days. The category compliance pointer and its official source are included per market. Each market also says how much TradeGraph knows there (rules_coverage: national, bloc, pointers or none, where none is not a clearance and how_to_check lists where to look); where it has no rule note, rule_pointers gives official-source starting points for blocs and countries such as the EAEU (Kazakhstan, Russia, Belarus, Armenia, Kyrgyzstan), the Andean Community, Mexico, Chile, Argentina, Türkiye, Egypt, Israel, South Africa, Nigeria, Kenya, Pakistan, Bangladesh, New Zealand, Uzbekistan and Mongolia, gate marking what must be met before import or sale. Omit country to check every market in the plan's table. Starting points, not legal advice. Free, read-only.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "item": "<item>"
    },
    "name": "blind_spots"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemYesProduct as an HS4 code (e.g. '3304') or a name in English or Korean (e.g. 'sunscreen', '라면'). Names cover TradeGraph's 35 items; any other product works as a 4-digit HS code (e.g. '1905' biscuits, '2005' kimchi, '3305' shampoo) with live UN Comtrade imports.
traitsNoOptional: product traits, comma-separated, that change the rules within one HS code: sunscreen, whitening (also arbutin, kojic acid), vitamin_a (retinol), gel_nail (UV/LED gel, semi-cured strips), contact_lens (HS 9001: contact lenses, colour lenses), hair_dye, hair_loss, acne, antiperspirant, dandruff, fluoride (toothpaste), human_derived (human stem cell culture media, human placenta, cord blood: a ban in the EU, UK, China and ASEAN), stem_cell (stem cell culture media whose source is not named: check it), exosome, radio (Bluetooth, Wi-Fi, cellular), battery, meat, dairy, egg, aerosol, flammable, industrial or household (for HS codes that hold both, such as 8414 fans, compressors and vacuum pumps: picks machinery rules, trade fairs and buyer searches, or household-appliance ones). Also detected from item, product and description; the answer lists them in product_traits.
countryNoTarget country as ISO 3166-1 alpha-2 (e.g. 'US', 'JP') or an English/Korean name. Optional: omit to check the markets of the plan's table.
productNoOptional: the product's own name in English (e.g. 'vegan sunscreen').
descriptionNoOptional: the product as the user describes it, any language (e.g. '비건 선크림 SPF50', '할랄 인증 저가 립스틱', 'premium anti-aging ampoule already on Amazon US'). Used to detect product traits that change the rules within one HS code (see traits) and the concepts, price tier, certifications and markets already selling that change which market fits (product_profile, entry_paths).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / description / description
      Previous value: -"Optional: the product as the user describes it, any language (e.g. '비건 선크림 SPF50', 'Bluetooth speaker with a rechargeable battery', 'ramen with beef broth'). Used only to detect product traits that change the rules within one HS code (see traits)."New value: +"Optional: the product as the user describes it, any language (e.g. '비건 선크림 SPF50', '할랄 인증 저가 립스틱', 'premium anti-aging ampoule already on Amazon US'). Used to detect product traits that change the rules within one HS code (see traits) and the concepts, price tier, certifications and markets already selling that change which market fits (product_profile, entry_paths)."
  2. Changed1 schema field changed
    • changedInput schema / properties / traits / description
      Previous value: -"Optional: product traits, comma-separated, that change the rules within one HS code: sunscreen, whitening (also arbutin, kojic acid), vitamin_a (retinol), gel_nail (UV/LED gel, semi-cured strips), contact_lens (HS 9001: contact lenses, colour lenses), hair_dye, hair_loss, acne, antiperspirant, dandruff, fluoride (toothpaste), human_derived (human stem cell culture media, human placenta, cord blood: a ban in the EU, UK, China and ASEAN), stem_cell (stem cell culture media whose source is not named: check it), exosome, radio (Bluetooth, Wi-Fi, cellular), battery, meat, dairy, egg, aerosol, flammable. Also detected from item, product and description; the answer lists them in product_traits."New value: +"Optional: product traits, comma-separated, that change the rules within one HS code: sunscreen, whitening (also arbutin, kojic acid), vitamin_a (retinol), gel_nail (UV/LED gel, semi-cured strips), contact_lens (HS 9001: contact lenses, colour lenses), hair_dye, hair_loss, acne, antiperspirant, dandruff, fluoride (toothpaste), human_derived (human stem cell culture media, human placenta, cord blood: a ban in the EU, UK, China and ASEAN), stem_cell (stem cell culture media whose source is not named: check it), exosome, radio (Bluetooth, Wi-Fi, cellular), battery, meat, dairy, egg, aerosol, flammable, industrial or household (for HS codes that hold both, such as 8414 fans, compressors and vacuum pumps: picks machinery rules, trade fairs and buyer searches, or household-appliance ones). Also detected from item, product and description; the answer lists them in product_traits."
  3. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds substantial context beyond them: the per-rule payload (kind, gate, who must act, applies-from date, official source, checked date), the 180-day staleness rule, and the meaning of rules_coverage levels. It also discloses provenance and the epistemic limit ('starting points, not legal advice'), which is exactly the kind of trust calibration structured fields cannot carry.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

It is front-loaded with the purpose and rewardingly dense, but the whole thing is one sprawling sentence-choked paragraph with long parenthetical example lists, which makes it hard to scan. The enumeration of blocs and countries, while useful, is bulk that could be compressed or moved out.

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?

There is no output schema, and the description compensates by describing the return shape in detail: per-rule fields, the gate flag, the category compliance pointer and source per market, rules_coverage plus how_to_check, and rule_pointers where no rule note exists. For a five-parameter, open-ended regulatory query this is complete enough to call correctly.

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 a baseline of 3 applies, but the description adds genuine meaning: it explains that rules are triggered either by the exact HS code or by a trait passed via description/traits, that traits are also auto-detected from item/product/description, and that the answer echoes them in product_traits. Those are behavioral semantics of the parameters, not restatements.

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 opening clause names the exact job — surfacing what a Korean exporter 'is likely to miss in a market' beyond category compliance — and the body enumerates the specific classes it covers (sale-blocking rules, pre-import approvals, extra duties, filings/labels, Korea-side checks). This is far more specific than a sibling like country_brief, and an agent can tell the two apart without opening either schema.

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

Usage Guidelines3/5

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

There is some operational guidance — 'Omit country to check every market in the plan's table', and 'Starting points, not legal advice' — plus an interpretation rule that rules_coverage 'none is not a clearance'. What is missing is routing: no sentence says when to reach for this tool versus country_brief, market_scan or export_workflow, and no exclusions are stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.