Skip to main content
Glama

China's applied import tariff for a 6-digit HS code

logistics_china_customs_tariffs
Read-only

China's applied import tariff for a 6-digit HS code from the World Bank WITS tariff database (UNCTAD TRAINS, as reported by China): MFN simple average, minimum and maximum duty rate across the national tariff lines, number of lines and the year. HS-6 level, not the 8/10-digit China customs line; VAT, consumption tax and retaliatory surcharges are not included. Another reporting country can be chosen with its ISO numeric code. Related tools on this server, for a different need: energy_world_customs_tariff_wits when you need applied import tariffs from the World Bank WITS / UNCTAD; logistics_japan_customs_tariff when you need Japan Customs import tariff lines for an HS heading. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

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": {
      "hs": "<hs>"
    },
    "name": "logistics_china_customs_tariffs"
  }
}

Input Schema

NameRequiredDescriptionDefault
hsYes6-digit HS code, e.g. 731815 (bolts)
reporterNoOptional ISO numeric country code of the importer (default 156 = China), e.g. 392 Japan, 356 India

Output Schema

NameRequiredDescriptionDefault
hsNo
yearNo
sourceNo
reporterNo
checkedAtNo
maxRatePctNo
minRatePctNo
tariffTypeNo
tariffLinesNo
nomenclatureNo
simpleAveragePctNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint, and the description adds materially: the underlying source and reporting basis, coverage exclusions, and the commercial/payment model ($0.002 USDC per successful call via x402 on Base, Solana or Arc; failed calls not charged). The last point is operationally important for an agent deciding whether to retry.

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?

A single dense paragraph that front-loads what is returned and follows with scope limits, alternatives, then price. Minor bloat in the sibling preamble and the multi-chain payment detail, but every clause carries information an agent would otherwise have to infer.

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 two-parameter lookup with an output schema, this covers everything needed: source provenance, aggregation semantics, geographic default, granularity caveat, tax exclusions, alternative tools and cost. Nothing essential to correct invocation is missing.

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 both parameters are already documented. The description still contributes meaning: it clarifies that the HS code must be 6-digit (not the national 8/10-digit line) and that the reporter slot selects an alternative reporting country via ISO numeric code, which disambiguates the default-China behavior.

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-like operation (retrieve China's applied import tariff) on a specific resource (6-digit HS code) and names the data source (World Bank WITS / UNCTAD TRAINS as reported by China). It also enumerates exactly what is returned (MFN simple average, min, max, line count, year), so the agent can tell it apart from Japan/EU tariff siblings without opening a schema.

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 routes the agent: use energy_world_customs_tariff_wits for other WITS/UNCTAD applied tariffs and logistics_japan_customs_tariff for Japan Customs tariff lines at HS heading level. It also states scope limits (HS-6 not the 8/10-digit China customs line; VAT, consumption tax and retaliatory surcharges excluded), which tells the agent when this tool is not sufficient.

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.

Resources