Skip to main content
Glama

List EU tariff quota tables

trade_list_quotas
Read-onlyIdempotent

Returns EU steel and safeguard tariff quota rows taken from the tables of official Official Journal acts: order number, product, CN codes, country, tonnes per period and out-of-quota duty. Use it for allocated quota volumes; use trade_list_measures for the regulations themselves, and TARIC for live remaining balances. Inputs (all optional, they narrow together): cn (CN/TARIC code, 4 to 10 digits, e.g. 7208; matches broader and narrower codes on the first 8 digits), country (name part, e.g. India), order_number (e.g. 09.9801), celex (exact act, e.g. 32026R1457), history (true also returns rows replaced by later acts; default false keeps the newest act per order), limit (1 to 50, default 20) and cursor (next_cursor, same filters; paging only, not a change checkpoint). Output: quotas[] with order_number, product, CN codes, country, period tonnes, duty and act URL, plus count, has_more, next_cursor and feed freshness (checked about once a day). Not live quota availability. Terms: read-only; MCP calls are never charged. Without a key, metered routes give 10 successful answers a day free, as short samples (up to 3 records, without file proof, history or paging cursor) where a paid HTTP address exists (unmetered routes are unlimited); errors do not count. On the paid HTTP routes, errors are free, and so are empty answers except a sanctions name search with no match when every loaded list it checks is fresh (lists not loaded yet are named in the answer). An optional API key keeps its prepaid-credit policy. When the free answers run out, the error names the HTTP alternative.

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_list_quotas"
  }
}

Input Schema

NameRequiredDescriptionDefault
cnNoCN/TARIC code, 4 to 10 digits after removing spaces and dots, e.g. 7208 or 72085120
celexNoExact regulation CELEX: 3 + four-digit year + R + four digits, e.g. 32026R1457; omit for all acts
limitNoQuotas per page, 1 to 50 (default 20); e.g. 20.
cursorNoOpaque next_cursor from this tool's prior answer; q followed by 1 to 6 digits, e.g. q0. Keep filters unchanged; omit on first call.
countryNoCountry name substring, 3 to 60 Unicode letters or spaces/punctuation (period, apostrophe, parentheses, hyphen), e.g. India; omit for all countries
historyNoAlso rows replaced by later acts (default false)
order_numberNoQuota order number, e.g. 09.9801

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already cover read-only/idempotent safety, but the description adds real behavioral context: feed freshness about once a day, history default behavior (newest act per order), cursor as paging-only not a change checkpoint, and free-tier limits. The lengthy metering/pricing paragraph is tangential to invocation semantics, which keeps it from a 5.

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?

Core purpose, alternatives, inputs and output shape are front-loaded and information-dense. The trailing free-tier/paid-route boilerplate is long and largely repeats schema or service-level policy, mildly diluting conciseness.

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?

For a read-only list tool with no output schema and 7 optional parameters, the description supplies the return structure (quotas[] fields plus count, has_more, next_cursor, freshness) and the narrowing behavior of all inputs. Nothing essential is missing.

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 100%, so baseline is 3, but the description adds meaning beyond the schema: cn matches broader and narrower codes on the first 8 digits, history returns rows replaced by later acts while the default keeps only the newest act per order, and cursor is paging-only. These are genuine semantic additions.

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?

Opens with a specific verb and resource (returns EU steel and safeguard tariff quota rows from Official Journal acts) and enumerates the returned fields, so it is immediately distinguishable from trade_list_measures.

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

Usage Guidelines5/5

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

Explicitly states when to use it (allocated quota volumes) and names the alternatives with their roles: trade_list_measures for the regulations themselves, TARIC for live remaining balances. It also adds the negative guideline 'Not live quota availability.'

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