Skip to main content
Glama

comtrade_list_reporters

Read-onlyIdempotent

List UN Comtrade reporters and their reporter codes, with optional text search to find the right code for trade data queries.

Instructions

List the reporters UN Comtrade has trade data from, with the codes reporter_code takes.

Answered from upstream's Reporters.json as packaged with this version (reference/Reporters.json), without an upstream call; meta.retrieved_at is when the package fetched it, meta.vintage is None. 255 rows when packaged, one per reporter code, current and historical (entry_expired_date is set on codes no longer used, such as 280 Fed. Rep. of Germany until 1990 or 810 USSR). Codes are UN Comtrade's, not always ISO numeric: 757 Switzerland (not 756), 842 USA, 276 Germany, 156 China; 97 European Union and 975 ASEAN are groups (is_group). search finds a code without reading the whole list.

Args: search: Keep the rows where this text occurs, ignoring case, in the code (reporter_code), the ISO alpha-3 code or the names (text, reporter_desc, reporter_note), e.g. "switz", "757", "CHE" (757 Switzerland, and 690 Seychelles by its name), "germany" (276 Germany, 278 and 280 until 1990). Omit for every row.

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

Input Schema

NameRequiredDescriptionDefault
searchNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

Goes well past the annotations: it discloses the data source (upstream Reporters.json packaged with this version, no upstream call), the row count (255, current and historical), what `entry_expired_date` means for retired codes (280, 810), and that `is_group` marks aggregates like 97 EU and 975 ASEAN. It also supplies the meta fields returned (retrieved_at, vintage=None), which the annotations cannot convey. The only mild tension is that openWorldHint=true while the description says no upstream call is made, but that reflects domain openness rather than a genuine conflict.

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?

Front-loads the purpose in the first clause, then layers source provenance, code quirks, and an Args block in a sensible order. Slightly over-detailed in places — noting that `meta.vintage` is `None` and the exact reference file path adds bulk an agent may not need — but no sentence is truly wasteful.

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?

With no output schema, the description still enumerates the returned fields (reporter_code, text, reporter_desc, reporter_note, is_group, entry_expired_date, meta) and their semantics, so an agent knows what it will get. For a one-parameter reference-list tool it leaves nothing material unexplained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and the single parameter is undocumented in the schema, so the description carries the full burden and does: case-insensitive matching against reporter_code, the ISO alpha-3 code, and the text/desc/note fields, with worked examples ('switz', '757', 'CHE', 'germany') and the omit-for-all-rows default. This is meaningfully more than the schema's bare string type.

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?

States a specific verb and resource — list the reporters UN Comtrade has data for — and immediately ties the output to the `reporter_code` values other tools consume. The resource is unambiguous against the sibling list tools (classifications, codes, commodities, partners), so an agent can select it 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 only implied: it is clearly a code-resolution/lookup tool, and the last line notes that `search` avoids reading the whole list. There is no explicit when-to-use statement (e.g., 'call this before comtrade_get_data to resolve reporter codes') and no exclusion against alternatives such as comtrade_list_partners or comtrade_list_codes, so routing is left to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.