Skip to main content
Glama

TradeStats - customs trade statistics

get_item_summary

One-call overview of a product (HS2/4/6 or national code) of one reporter for the usual questions: a one-line summary (ai_context_summary, in US dollars), latest month, the last 12 months against the previous 12 and 3 years earlier, top 20 partners plus "other", the fastest growing and declining partners, calendar-year totals, partner concentration, new markets, the seasonal peak and trough months (or seasonality_unavailable_reason) and an anomaly signal, with notes on gaps and non-comparable periods. Precomputed monthly; use it right after search_items (or first, when you know the code) instead of several separate calls (e.g. semiconductor manufacturing machines 848620 for export, pharmaceuticals chapter 30 for import). get_item_summary is about one product; get_catalog is about the whole service (coverage, latest month, your limits), so call get_catalog for those and this tool for a product. For other months, a single partner country or details use get_series, get_partners, get_ranking, get_new_markets, get_seasonality. value_basis says on which basis the reporter's own values are (for example the US import value is the customs value without freight and insurance); compare_countries restates imports on a CIF basis, so its totals can differ by about 1-2% from this answer. Customs trade statistics of several reporting countries (Japan JP, United States US, United Kingdom GB, European Union (27 member states) EU) from their official customs data, monthly, by HS product code and partner country. value fields are in the reporter's currency (currency: JPY, USD, GBP or EUR) and _usd fields in US dollars; ratios and shares are fractions precomputed from the full dataset; every answer carries reporter, currency, data_through (latest published month), the reporter's attribution, and notes. Maximum 200 rows per answer. Numbers in answers are rounded once, at the end: amounts (value, _usd, v12 ...) to 2 decimals, quantity and kg to 3, unit prices (unit_price) to 4 significant digits below 100 and 2 decimals from 100 up (never rounded to 0), and ratios, shares and growth rates (yoy, mom*, share*, hhi*, chg3y) to 6; whole numbers and null are left as they are. A null quantity, kg or unit price comes with a *_unavailable_reason (mixed_units, weight_only, no_quantity_in_source, no_weight_in_source, source_gap, withheld; get_catalog lists them in null_reasons), and a missing seasonality with seasonality_unavailable_reason. The national level (JP 9-digit, US 10-digit, GB 8-digit codes) differs between reporters and between import and export; EU has no national level (HS6 only); HS6, HS4 and HS2 are shared. Import and export are separate datasets, so reporter and flow are always required for product figures. Rankings (limit) are limited to the top 20 without an API key (more is refused with out_of_scope) and to 100 with a free API key. Start with get_catalog (coverage, your access limits, which tool to use) or, when you already know the code, get_item_summary for a one-call overview of a product.

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": {
      "reporter": "<reporter>",
      "flow": "<flow>",
      "code": "<code>"
    },
    "name": "get_item_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesHS product code with 2, 4 or 6 digits, or the reporter's national code (JP 9 digits, US 10, GB 8; a reporter without a national level, such as EU, has HS6 as its finest level); dots are ignored (e.g. "85", "8507", "850760" or "8507.60"). National codes differ between reporters and between import and export; find codes with search_items. On a build that serves HS6 and above a national code without a series answers fine_digits_not_served: retry with its 6-digit parent.
flowYesRequired. "import" (goods entering the reporting country) or "export" (goods leaving it); there is no combined view: "both" does not exist. For a comparison across countries use compare_countries, for exports minus imports use get_balance.
reporterYesRequired. The reporting country whose customs statistics are read: "JP" (Japan), "US" (United States), "GB" (United Kingdom) or "EU" (European Union (27 member states)). Partners are the other countries.

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?

With no annotations, the description carries the full behavioral burden and does so thoroughly: it states that results are precomputed monthly, that answers carry reporter, currency, data_through, attribution, and notes, that there is a 200-row cap, that ranking limits are 20 without an API key and 100 with a free key, and that excess requests are refused with out_of_scope. It also discloses rounding rules, null-reason codes, national-code differences between reporters, and that import and export are separate datasets.

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

Conciseness3/5

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

The purpose and usage guidance are front-loaded, but the description is extremely long and dense, with some repetition of get_catalog and get_item_summary usage near the end. The detailed rounding and null-reason paragraphs are useful context but make the definition harder to scan than necessary.

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?

There is no output schema and no annotation coverage, so the description must explain both what is returned and how to interpret it. It does that comprehensively, covering output fields, currency and value bases, rounding, null reasons, data coverage, reporter differences, and access limits.

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 three required parameters are already well documented in the schema, including enums and explanations for code, flow, and reporter. The description adds examples such as 848620 for export and chapter 30 for import, but most parameter meaning is already in the schema, so the baseline of 3 is appropriate.

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 opens with a specific verb and resource: a one-call overview of one product for one reporter, listing exactly the outputs (summary, latest month, comparisons, partners, seasonality, anomaly signal). It explicitly distinguishes this from sibling tools such as get_catalog, get_series, get_partners, get_ranking, get_new_markets, and get_seasonality.

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?

It gives explicit when-to-use guidance: right after search_items, or first when the code is known, instead of several separate calls. It also names alternatives and the conditions that select them, including get_catalog for service-wide questions and get_series/get_partners/get_ranking for other months or single-partner detail.

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