Skip to main content
Glama
Sign In

TradeStats - customs trade statistics

by dev.tradestats
OverviewDiscussionsAdmin

list_indicators

Call by name, no HS code needed: lists the named indicators this service computes from public customs statistics (for example the quarterly base price of domestic naphtha, naphtha import prices and origins, or Japan passenger car and parts exports by destination). Each entry has its id, aliases in English and Japanese, definition, how often it is published, the caveats, the latest month and whether it can be computed in this build (status ok, not_computable with a reason, or not_built). Use it first to find the id or alias to give to get_indicator; narrow the list with reporter or with words in query. The values are our own calculations, not official published figures.

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

Input Schema

NameRequiredDescriptionDefault
queryNoOptional. Words that must all appear in the indicator id, alias (English or Japanese), title or definition, for example "naphtha" or "cars".
reporterNoOptional. List only the indicators of this reporting country: "JP", "US", "GB" or "EU". Omit for all deployed reporters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it enumerates what each entry contains (id, EN/JP aliases, definition, publication frequency, caveats, latest month), discloses the three-valued status field including the not_computable-with-reason case, and warns that values are in-house calculations rather than official figures. It falls short only on list size, ordering, and pagination behaviour for what is presumably a long catalog.

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-loaded with the key framing ("Call by name, no HS code needed") and packed into one dense paragraph with no filler sentences. The long example list of indicator types is slightly padded and could be trimmed without loss.

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 and no annotations, the description must explain the return shape, and it does so entry-by-entry including the status values and the accuracy caveat. Only the scale of the response and any pagination or ordering behaviour are left unstated, which matters for an agent planning to call it before get_indicator.

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 coverage is 100%, so both parameters are already documented in the schema; the description largely restates the all-words-must-match semantics of query and the reporter narrowing. It adds little parameter meaning beyond the schema, so the baseline applies.

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 ("lists the named indicators this service computes from public customs statistics") and immediately differentiates itself from get_indicator by positioning itself as the lookup step. The parenthetical examples (naphtha base price, import origins, Japan car exports) make the resource concrete rather than abstract.

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 says "Use it first to find the id or alias to give to get_indicator," naming the downstream tool and the ordering between them. It also gives the narrowing levers (reporter, words in query) and the "no HS code needed" contrast, so an agent knows exactly when this tool rather than an item-search tool applies.

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

All TradeStats - customs trade statistics toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources