Skip to main content
Glama

Returns UK Global Tariff data for a 6–10-digit commodity

tariff_uk
Read-only

Returns UK Global Tariff data for a 6–10-digit commodity code via the UK Trade Tariff API (OGL v3): description, third-country duty rate, VAT, measures, and preferential rates for a given origin country. Text search (q) returns matching commodity headings. Coverage: UK only, post-Brexit schedule. Related tools on this server, for a different need: tariff_us when you need to search the US tariff schedule (HTS) by number or words. Price: $0.003 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tariff_uk"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoKeyword search for commodity headings (max 200 characters)
codeNo6–10-digit commodity code (e.g. 8471300000). Omit to use q.
originNoOptional ISO-2 country code for preferential duty lookup (e.g. US, CN)

Output Schema

NameRequiredDescriptionDefault
urlNo
vatNo
codeNo
sourceNo
validToNo
measuresNo
checkedAtNo
validFromNo
disclaimerNo
parentCodeNo
descriptionNo
thirdCountryDutyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior3/5

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

The annotations already declare readOnlyHint and openWorldHint, so the read-only, external-data nature is covered structurally; the description adds genuinely useful non-schema facts: OGL v3 licensing, UK-only scope, and a per-call price of $0.003 with failed calls free, plus the x402/USDC payment mechanism. That payment detail matters because a caller needs a funded wallet, but it is not stated as a prerequisite or failure mode, and nothing is said about rate limits or result caps.

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?

Front-loaded with purpose and scope, followed by search-mode note, coverage limit, alternative tool, and pricing in a logical order. The final pricing sentence is long and packs three facts (price, currency/networks, refund policy) into one clause, but nothing is redundant.

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?

With an output schema present, the description doesn't need to detail return values, yet it still summarizes the key fields, and it covers scope, sibling routing, and cost. What's missing is the operational edge case implied by zero required parameters: what error or behavior results when neither `q` nor `code` is passed.

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 baseline is 3 regardless. The description reinforces that `q` is a text search returning matching commodity headings and that `origin` drives preferential-rate lookup, but adds no format, length, or disambiguation rules beyond what the schema already spells out (max 200 chars, ISO-2, omit code to use q).

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 (returns UK Global Tariff data for a 6–10-digit commodity code), enumerates what the response contains (description, third-country duty rate, VAT, measures, preferential rates), and names the differing sibling tariff_us by data set. An agent can distinguish it from tariff_us and from the generic vat tool without opening any 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?

Explicitly scopes coverage to the UK post-Brexit schedule and routes US-schedule lookups to tariff_us. It also clarifies that `q` is the mode for fuzzy/text lookup while `code` is the lookup-by-number path, though it never states which of the two is preferred when both could apply or what happens if neither is supplied (0 required params).

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