Skip to main content
Glama

UK Data: UK trade, property and planning

trade_tariff

Read-onlyIdempotent

Find a UK commodity code by description, or get duty rates and import measures for a code. (cost: 2 credits)

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": "trade_tariff"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNostring
commodityCodeNostring: 4-digit heading lists its codes, 10-digit code gives duties

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral context by disclosing the credit cost ('cost: 2 credits') and naming the payload ('duty rates and import measures'), though it says nothing about failure behavior for unknown codes or result paging.

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?

A single front-loaded sentence covers both modes, with the cost disclosure appended as a short parenthetical. Nothing is redundant or padded.

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?

For a read-only two-parameter lookup with no output schema, the description supplies purpose, both input modes, the nature of the return payload and the cost. The remaining gap is the interaction between the two optional parameters and what happens on a miss, which an agent would have to learn by trial.

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 nominally 100%, but the 'query' entry is documented only as 'string', so the description carries real weight by clarifying that it accepts a plain-language description. The commodityCode semantics (4-digit heading lists codes, 10-digit gives duties) live in the schema, and the description does not address that both parameters are optional and presumably mutually exclusive.

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 and resource ('Find a UK commodity code') and enumerates both capabilities: description-based lookup and code-based duty/measures retrieval. No sibling in the list covers UK trade tariffs, so an agent can identify this tool unambiguously without opening the 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?

The two call modes ('by description' vs 'for a code') give clear context for when each input path applies, and the schema's commodityCode note reinforces the 4-digit vs 10-digit split. It stops short of explicit exclusions or stating which parameter wins if both are supplied, so it is clear context rather than full routing guidance.

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