Skip to main content
Glama

Trade & public tenders

UK Trade Statistics: Trade with a country

uk-trade-stats__country
Read-onlyIdempotent

UK imports from and exports to one country for a month or year: totals and top HS2 product chapters. A few free samples a day, then $0.003 USDC per call via x402.

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": {
      "country": "<country>"
    },
    "name": "uk-trade-stats__country"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNoChapters to list (default 15, max 50)
periodNoYYYY, YYYY-MM or "latest" (default latest month)
countryYesPartner country, ISO alpha-2

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint), so the bar is lower. The description adds genuinely useful behavior beyond them: a metered x402 payment model with a few free samples per day and $0.003 USDC per call, which an agent must know before invoking.

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?

Two tight sentences with no waste: the data scope is front-loaded and the payment model follows. Every clause earns its place.

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 a full annotation set and an output schema present, the description needn't explain return values, and it covers the cost/auth dimension. The one remaining gap is routing guidance relative to the two sibling uk-trade-stats tools.

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 parameters (top, period, country) are already documented in the schema; this sets the baseline at 3. The description only loosely reinforces the dimensions ('for a month or year', 'top HS2 product chapters') without adding format or constraint detail beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb+resource: 'UK imports from and exports to one country', with scope (month or year) and payload (totals and top HS2 product chapters). It implicitly separates itself from uk-trade-stats__commodity by the 'country' dimension, but never names or contrasts with the sibling tools explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is only implied — 'Trade with a country' tells you the query dimension but gives no when-to-use, when-not-to-use, or direction to uk-trade-stats__commodity / uk-trade-stats__latest for other slices. The pricing sentence is cost guidance, not selection 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