Skip to main content
Glama

Japan Trade Statistics (customs data)

by com.washutrading.data
OverviewDiscussionsAdmin

Get partner countries

get_partners
Read-onlyIdempotent

Partner-country breakdown and shares for an item (one month or the last 12 months): destinations for exports, origins for imports. / 品目の相手国の内訳とシェア（その月、または直近12か月）。輸出なら輸出先、輸入なら輸入元。

Input Schema

NameRequiredDescriptionDefault
codeYes統計品目番号（9桁・6桁・4桁）か類（2桁）・部の番号。分からなければ search_items で探す / Statistical code (9, 6 or 4 digits) or chapter (2 digits) or section; use search_items to find it
flowYesexport＝輸出、import＝輸入 / export or import
langNo答えの言葉（ja＝日本語・既定、en＝英語） / Response language (ja default, en)
sortNovalue＝金額の順（既定）、growth＝直近12か月の伸びの順（下限つき） / value (default) or growth: fastest-growing partners over the last 12 months (with a minimum)
levelNo区切り（省略時はコードの桁数で判断） / Level (inferred from the code length if omitted)
limitNo返す相手国の数の上限 / Maximum number of partners
monthNo月（YYYY-MM。省略時は最新の月） / Month as YYYY-MM (latest if omitted)
windowNo1＝その月、12＝その月までの直近12か月 / 1 = that month, 12 = the last 12 months up to that month
min_valueNo下限（ドル、直近12か月か前の12か月。既定 1,000,000） / Minimum value in USD (last 12 months or the 12 before; default 1,000,000)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / code / description
      Added value: +"統計品目番号（9桁・6桁・4桁）か類（2桁）・部の番号。分からなければ search_items で探す / Statistical code (9, 6 or 4 digits) or chapter (2 digits) or section; use search_items to find it"
    • addedInput schema / properties / lang / description
      Added value: +"答えの言葉（ja＝日本語・既定、en＝英語） / Response language (ja default, en)"
    • addedInput schema / properties / limit / description
      Added value: +"返す相手国の数の上限 / Maximum number of partners"
    • changedInput schema / properties / month / description
      Previous value: -"YYYY-MM"New value: +"月（YYYY-MM。省略時は最新の月） / Month as YYYY-MM (latest if omitted)"
    • addedInput schema / properties / window / description
      Added value: +"1＝その月、12＝その月までの直近12か月 / 1 = that month, 12 = the last 12 months up to that month"
  2. Changed3 schema fields changed
    • addedInput schema / properties / limit
      Added value: +{
+  "maximum": 200,
+  "minimum": 1,
+  "type": "integer"
+}
    • addedInput schema / properties / min_value
      Added value: +{
+  "description": "下限（ドル、直近12か月か前の12か月。既定 1,000,000） / Minimum value in USD (last 12 months or the 12 before; default 1,000,000)",
+  "minimum": 0,
+  "type": "number"
+}
    • addedInput schema / properties / sort
      Added value: +{
+  "description": "value＝金額の順（既定）、growth＝直近12か月の伸びの順（下限つき） / value (default) or growth: fastest-growing partners over the last 12 months (with a minimum)",
+  "enum": [
+    "value",
+    "growth"
+  ],
+  "type": "string"
+}
  3. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish that this is a read-only, idempotent, non-destructive operation. The description adds useful domain behavior by clarifying that exports return destinations, imports return origins, and results include shares over either one month or twelve months.

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 compact and front-loaded, with the core operation and output scope stated immediately. The bilingual repetition is reasonable for the tool's localization and does not obscure the main point.

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?

For a read-only analytical tool with complete parameter descriptions and no output schema, the description gives enough context to understand the operation and output dimension. It could be stronger by naming the sibling alternatives or clarifying what 'shares' means precisely.

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 nine parameters. The description adds some semantic meaning for flow and time window, but it does not explain many other parameters such as sort, level, limit, or min_value beyond what the schema provides.

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 states a specific resource and scope: partner-country breakdown and shares for an item, with distinct export/import direction. It is clear what the tool returns, but it does not explicitly distinguish itself from siblings such as get_country_summary, get_ranking, or get_series.

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?

It gives contextual signals such as one month vs. last 12 months and destinations for exports vs. origins for imports. However, it does not explicitly say when to use this tool instead of sibling tools like get_country_summary or get_ranking.

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

All Japan Trade Statistics (customs data) 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