supply-chain-mcp-server

get_trade_flow

Retrieve trade data between two countries for a specific product category, including volume, value, and top partners, to analyze import or export flows.

Instructions

Ruft Handelsdaten zwischen zwei Ländern für eine Produktkategorie ab.

Args: reporter_country: Berichtendes Land (z.B. "deutschland", "usa", "china") partner_country: Handelspartner ("all" für alle, oder Ländername) product_category: Kategorie (elektronik/maschinen/autos/pharma/stahl/oel/halbleiter) year: Jahr (Standard: 2023) flow: "import" oder "export"

Returns: Handelsdaten: Volumen, Wert, Top-Partner

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_country": "<reporter_country>"
    },
    "name": "get_trade_flow"
  }
}

Input Schema

Name	Required	Default
`reporter_country`	Yes
`partner_country`	No	all
`product_category`	No	elektronik
`year`	No
`flow`	No	import

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 11, 2026

TDQS

A4/5.0

Behavior3/5

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

No annotations exist, and the description does not disclose behavioral traits like read-only nature, rate limits, or authentication needs, but it does describe the return structure (volume, value, top partners).

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?

The description is appropriately sized with a clear Args/Returns structure, though it could be slightly more concise.

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?

Given the absence of output schema and annotations, the description provides adequate context for all parameters and return values, though it could mention data source or update frequency.

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?

With 0% schema coverage, the description fully compensates by explaining each parameter with examples and defaults, adding significant meaning beyond 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 clearly states the tool retrieves trade data between two countries for a product category, effectively distinguishing it from siblings that provide country-level stats or top partners.

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 implied through parameter descriptions, but no explicit guidance on when to use this tool vs alternatives or exclusions is provided.

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

Deploy Server