Skip to main content
Glama

BRAINIAC Tariffs & Trade Reference

Look up UK Global Tariff duty

trade-tariff_uk-global-tariff-lookup
Read-onlyIdempotent

Return the UK Global Tariff third-country (measure type 103) duty for a UK commodity code from a vendored DBT dataset subset. Preferential rates are not included. Price $0.02 USDC. POST /api/v1/trade-tariff/uk-global-tariff-lookup. An unpaid call returns the x402 payment terms and does not run.

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": {
      "commodityCode": "<commodityCode>"
    },
    "name": "trade-tariff_uk-global-tariff-lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNodate, string. Optional.
commodityCodeYescommodityCode, string. Required.

Output Schema

NameRequiredDescriptionDefault
dateNodate. String.
foundNofound. Boolean.
sourcesNosources. Array.
measuresNomeasures. Array.
limitationsNolimitations. Array.
commodityCodeNocommodityCode. String.
datasetVersionNodatasetVersion. String.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing the data provenance (a vendored DBT dataset subset), a coverage limitation, a per-call price of $0.02 USDC, the POST endpoint, and the critical failure mode: an unpaid call returns x402 payment terms and does not execute. The x402 payment gate and non-execution behavior are exactly the kind of trait an agent cannot infer from readOnlyHint/idempotentHint.

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

Conciseness5/5

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

Four short sentences, front-loaded with the core purpose, followed by exclusions, cost, and the payment caveat in priority order. Every sentence carries distinct information with no repetition of the title or schema.

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?

Return values are covered by the output schema, and the description supplies the remaining context an agent needs before calling: cost, payment precondition, data source, and rate-type limitation. Nothing material for correct invocation is missing.

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 both parameters and their patterns are already documented in the schema. The description adds only that the code is a UK commodity code, which is marginal over the structured data; baseline 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?

States a specific verb and resource ('Return the UK Global Tariff third-country (measure type 103) duty for a UK commodity code') and pins down the exact measure type and jurisdiction. This clearly separates it from the US-focused siblings such as trade-tariff_us-hts-duty-rate-lookup.

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?

Gives a clear scope exclusion — 'Preferential rates are not included' — so an agent knows this is not the tool for preferential/agreement rates, and the 'vendored DBT dataset subset' framing sets expectations about source and coverage. It stops short of naming an alternative tool for preferential rates, so it is clear context without explicit routing.

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