tollbooth

trade_flows

UN Comtrade trade flows: import/export values and partner breakdowns by reporter country, HS code and year.

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_code": "<reporter_code>",
      "cmd_code": "<cmd_code>",
      "period": "<period>"
    },
    "name": "trade_flows"
  }
}

Input Schema

Name	Required	Description
`period`	Yes	Year e.g. 2024
`cmd_code`	Yes	HS commodity code e.g. 8471
`flow_code`	No	M=import X=export M,X=both. Default M
`partner_code`	No	Partner country code
`reporter_code`	Yes	UN country code e.g. 842=USA

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 24, 2026

TDQS

B3.3/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses the upstream source (UN Comtrade) and the kinds of data returned, but says nothing about return format, units, data availability, rate limits, or whether the call is read-only.

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

Conciseness5/5

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

The description is a single front-loaded sentence with no wasted words. It immediately states the resource and the key dimensions.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With five parameters, three required, no output schema, and no annotations, the description covers the core query dimensions. However, it omits return-value structure, units, and data coverage details that an agent would need to use the results correctly.

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 schema already documents all five parameters and the flow_code enum. The description reinforces the core dimensions (reporter country, HS code, year, partner breakdowns) but adds no syntax or meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource (UN Comtrade trade flows) and specifies the data dimensions: import/export values and partner breakdowns by reporter country, HS code, and year. It is clear what the tool returns, but it does not explicitly differentiate itself from any of the many sibling data-retrieval tools.

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

Usage Guidelines2/5

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

There is no explicit guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. The intended use is implied by the resource name, but an agent must infer it.

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

All tollbooth tools Inspect

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

Need Help?