Trustbase Lab · rCB & Chemical Recycling Data

Search Bilateral Trade Flows

query_trade_flows

Read-onlyIdempotent

Purpose: query global carbon black (HS 280300) bilateral trade flows from UN Comtrade official customs statistics - 1751 records, 8 reporters (CHN/USA/DEU/JPN/KOR/IND/THA/TUR) plus World totals, 2024-2025. Guidelines: pass reporter (ISO3 alpha), partner (ISO3/numeric/name), period (YYYY), flow (X=export/M=import) and limit; unit_price_usd_t and share_pct are derived fields (share excludes World); use for capacity shift, trade-partner concentration and price-gap structure analysis. Limits: customs-reported data only - no commercial quote platforms; unit prices with qty missing are flagged 'missing_qty'; guardrail band 300-8000 USD/t. Ex: 'China carbon black exports 2025', 'top US import partners HS 280300'.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`flow`	No	流向 X=出口 / M=进口
`limit`	No	返回条数上限（默认 20,最大 200）
`period`	No	期间 YYYY（如 2024），留空取全部
`partner`	No	伙伴国筛选：ISO3/数字代码/中文名（部分支持），如 THA/764/泰国
`reporter`	No	报告国 ISO3 字母码，如 CHN/USA/DEU/JPN/KOR/IND/THA/TUR
`response_format`	No	Output format: 'markdown' (default, human-readable) or 'json' (machine-readable).	markdown

Output Schema

TableJSON Schema

Name	Required	Description	Default
`text`	Yes	Human-readable result (markdown, or a JSON string when response_format=json).

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 20, 2026

addedInput schema / properties / response_format / description

Added value: +"Output format: 'markdown' (default, human-readable) or 'json' (machine-readable)."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "text": {
+      "description": "Human-readable result (markdown, or a JSON string when response_format=json).",
+      "type": "string"
+    }
+  },
+  "required": [
+    "text"
+  ],
+  "type": "object"
+}

AddedSep 17, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Beyond the read-only/idempotent annotations, the description discloses important behavioral and data-quality traits: customs-reported data only, derived fields, missing quantity handling ('missing_qty'), and a USD/t guardrail band. This gives agents substantial context for interpreting results and avoiding misuse.

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 organized with clear labeled sections (Purpose, Guidelines, Limits, Ex) and every sentence carries useful information. It is dense but not bloated, and the purpose is front-loaded.

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?

Given the tool's complexity and the presence of a full input schema and output schema, the description is complete: it covers dataset scope, supported values, derived fields, limitations, guardrails, and example queries. Nothing critical is missing for selecting and invoking the tool 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 coverage is 100% and the schema already describes each parameter, including flow enums and partner formats. The description adds some useful context like derived-field definitions and natural-language examples, but largely restates parameter guidance already present in the schema.

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 states a specific verb ('query'), a precise resource (global carbon black HS 280300 bilateral trade flows), and the data source (UN Comtrade official customs statistics). It also gives concrete scope details (1751 records, reporters, years) and examples, making it easy to distinguish from sibling trade tools.

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

Usage Guidelines4/5

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

It clearly describes when to use the tool: for capacity shift, trade-partner concentration, and price-gap analysis, and explicitly excludes commercial quote platforms. It does not name sibling tools as alternatives or state when not to use them, so it falls just short of a perfect score.

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

All Trustbase Lab · rCB & Chemical Recycling Data 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?