SiteCheck Trade & Energy

UK Global Tariff commodity lookup by 10-digit commodity

logistics_uk_trade_tariff

Read-only

UK Global Tariff commodity lookup by 10-digit commodity code from the official UK Trade Tariff API: description, chapter, validity dates, declarable flag and basic duty rate (null when the API leaves it empty). Full duty measures per trading partner are not expanded. Related tools on this server, for a different need: logistics_ftz_foreign_trade_zone when you need Pending US Foreign-Trade Zone Board applications with open; 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": {
      "code": "<code>"
    },
    "name": "logistics_uk_trade_tariff"
  }
}

Input Schema

Name	Required	Description	Default
`code`	Yes	10-digit UK commodity code, e.g. 0901110000 (must be an existing leaf code)

Output Schema

Name	Required	Description	Default
`code`	No
`source`	No
`chapter`	No
`validTo`	No
`checkedAt`	No
`validFrom`	No
`declarable`	No
`description`	No
`basicDutyRate`	No
`descriptionPlain`	No
`bindingRulingGuidance`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations only declare readOnly and openWorld, so the description carries real additional weight: it discloses the pay-per-call model ($0.002 USDC via x402 on Base/Solana/Arc), that failed calls are free, that duty rate can be null when the API leaves it empty, and that partner-level duty measures are not expanded. The remaining gap is the absence of any statement about error behavior or rate limits when the code is not a valid leaf.

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 core capability, return fields and scope limitation are front-loaded in the first two sentences, and the pricing note is useful rather than filler. The sibling-routing clause is overlong for its value and contains a truncated phrase ('with open') that costs clarity.

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?

The tool is simple (one required parameter) and has an output schema, so return values need not be fully explained, yet the description still flags the null duty-rate edge case and the missing partner-level measures. Combined with cost and alternative routing, an agent has everything needed to call it correctly and interpret the result.

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?

With a single parameter at 100% schema coverage, the schema already states it is a 10-digit UK commodity code and must be an existing leaf code. The description repeats 'by 10-digit commodity code' without adding format rules, validation behavior, or examples beyond what the schema provides, so the baseline of 3 applies.

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 names a specific verb (lookup), resource (UK Global Tariff commodity), key (10-digit commodity code) and source (official UK Trade Tariff API), then enumerates the exact fields returned: description, chapter, validity dates, declarable flag and basic duty rate. It also explicitly bounds scope (no per-partner duty measures), so an agent can distinguish it from logistics_japan_customs_tariff and logistics_eu_taric_consultation 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 Guidelines4/5

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

It routes the agent away from two siblings with explicit conditions ('logistics_japan_customs_tariff when you need Japan Customs import tariff lines'), which is genuine when-to-use guidance. However, those routes are framed as 'a different need' rather than as when NOT to use this tool, and the phrasing for the FTZ sibling ('with open') is garbled, leaving the other tariff siblings (China customs, EU TARIC, hs_code_classifier) unaddressed.

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

All SiteCheck Trade & Energy tools Inspect

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

Need Help?