Skip to main content
Glama

Get a product's production and trade

markets_products
Read-onlyIdempotent

A product's sold production (value and quantity) from PRODCOM by its 8-digit code, and its imports and exports from Eurostat's trade figures by its 8-digit CN code, by country and year; for the EU27, trade with countries outside the EU and the apparent consumption (production + imports - exports) with each figure's source. The UK's imports and exports by CN code from HMRC. Confidential figures are left out, never filled in. Nothing is charged when no figures come back. Costs $0.02 per call; nothing if it fails.

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

Input Schema

NameRequiredDescriptionDefault
cnNoIts 8-digit Combined Nomenclature code, e.g. 84198180, for trade.
yearsNoHow many recent years.
prodcomNoThe product's 8-digit PRODCOM code, e.g. 28931580.
countriesNoTwo-letter codes (DE, FR, NO...) and EU27_2020 for the whole EU; GB says what the UK publishes. EU27_2020 when left out.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations cover safety (readOnly, idempotent, non-destructive), and the description adds genuinely non-obvious behavior: confidential figures are omitted rather than imputed, there is no charge when no figures return, and pricing is $0.02 per call with failure being free. Missing pagination/return-shape details 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?

Dense and front-loaded, leading with the subject and sources before the cost/confidentiality caveats. A few clauses (e.g. the consumption formula) border on schema-level detail, but nothing is wasted.

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 no output schema, the description carries the return-value burden and does so reasonably—value and quantity, per country and year, with source attribution and computed apparent consumption. It stops short of describing result shape or fallback behavior when only one code is supplied.

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 description coverage is 100%, so the baseline is 3, but the description adds real semantic value by explaining *why* there are two code parameters: PRODCOM codes key production while CN codes key trade. It also notes the EU27 default behavior implicitly through the country scoping.

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?

Names the exact resources (sold production, imports/exports, apparent consumption) and the specific upstream sources (PRODCOM, Eurostat, HMRC), plus the keying scheme (8-digit PRODCOM vs CN code). An agent can distinguish this from markets_prices/markets_size 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 Guidelines3/5

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

Usage is implied by the data sources and the requirement for 8-digit codes, but the description never states when to prefer this over markets_size or markets_prices, nor any prerequisites or exclusions. The agent must infer selection from context.

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