EU Trade Explorer

Get Market Summary

get_market_summary

Report-section helper ("General overview"): condensed, report-ready digest of how a market has evolved over the chosen window -- one call instead of separately fetching and cross-referencing get_overview + get_reporter_detail + get_concentration + get_net_import_reliance yourself. Set query.frequency = "year" for a multi-year evolution summary (recommended over the model's default of "quarter").

Every figure reflects query exactly as given -- the same product/reporter/partner_set/period slice a dashboard user would have selected. Nothing here substitutes a different reporter or partner_set (e.g. to contrast intra-EU against extra-EU trade): call this again with a different query.partner_set for that, the same way a dashboard user would switch the sidebar's selector.

Returns {narrative_facts, chart_data, available, reason}. narrative_facts combines, for the flow selected by query.partner_set:

Headline trade: first/last/min/max/pct_change for export & import value, quantity and price, plus the trade-balance trend.
Partner concentration: first/last/pct_change of the value-based HHI for imports and exports.
Top partners and top EU reporters by value: each one's first/last/pct_change -- i.e. who is gaining or losing share.
Net import reliance: first/last/pct_change of the annual NIR % for query's own reporter/partner_set (only frequency is normalised to "year", since NIR is structurally annual and the upstream API always returns it that way regardless); omitted if the product has no PRODCOM mapping. chart_data carries the full-fidelity headline trade and top-partner/ top-reporter series for charting.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`query`	Yes	The product/reporter/partner-set/period/frequency slice to query -- the same request body every tradedashboard.eu analytical endpoint takes. See its own field descriptions (product, reporter, partner_set, period_start, period_end, frequency, n_top, ...) for details; only `product` is required, everything else has a sensible default.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedAug 5, 2026

removedInput schema / $defs

Removed value: -{
-  "DashboardQuery": {
-    "description": "Shared request body for every analytical endpoint.\n\nOne product (or a list of products to aggregate), one reporter (or group of\nreporters), a partner set, a period window and a frequency fully describe a\nslice of Eurostat Comext/PRODCOM data. Individual endpoints read extra,\nendpoint-specific options from the query string (e.g. ``entity_level``,\n``flow``, ``partner``) rather than from this body.",
-    "properties": {
-      "frequency": {
-        "default": "quarter",
-        "description": "Resampling frequency for the series: 'month', 'quarter' or 'year'.",
-        "title": "Frequency",
-        "type": "string"
-      },
-      "include_other": {
-        "default": true,
-        "description": "Bundle entities outside the top-N into a single 'Other' bucket.",
-        "title": "Include Other",
-        "type": "boolean"
-      },
-      "lang": {
-        "default": "en",
-        "description": "Language for translated labels in the response (en, de, fr, es, it, ro).",
-        "title": "Lang",
-        "type": "string"
-      },
-      "midpoint": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "Split point 'YYYY-MM' for the Pattern Shifts tab: the window is cut in two here and the before/after change per entity is reported. Defaults to the middle of the period when omitted.",
-        "title": "Midpoint"
-      },
-      "n_top": {
-        "default": 7,
-        "description": "Number of top entities (by volume/value) to break out individually in charts.",
-        "title": "N Top",
-        "type": "integer"
-      },
-      "partner_set": {
-        "default": "non-EU countries",
-        "description": "Named partner preset, e.g. 'non-EU countries', 'EU countries', 'all countries', or a predefined partner group.",
-        "title": "Partner Set",
-        "type": "string"
-      },
-      "partners": {
-        "anyOf": [
-          {
-            "items": {
-              "type": "string"
-            },
-            "type": "array"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "Explicit partner-country list that overrides 'partner_set' when present.",
-        "title": "Partners"
-      },
-      "period_end": {
-        "description": "Inclusive end of the analysis window, ISO month 'YYYY-MM'. Defaults to roughly three months ago — the latest period Eurostat typically has fully reported.",
-        "title": "Period End",
-        "type": "string"
-      },
-      "period_start": {
-        "default": "2015-01",
-        "description": "Inclusive start of the analysis window, ISO month 'YYYY-MM'.",
-        "title": "Period Start",
-        "type": "string"
-      },
-      "prodcom_code": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "Specific PRODCOM dataset code to pin for the Net Import Reliance and Trade Intensity tabs, when a single CN code maps to several. Ignored elsewhere.",
-        "title": "Prodcom Code"
-      },
-      "product": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "items": {
-              "type": "string"
-            },
-            "type": "array"
-          }
-        ],
-        "description": "Combined Nomenclature customs code(s), 2–8 digits, or the literal 'TOTAL' meta-aggregate (all products combined). Pass a list to aggregate several codes: their volumes are summed and prices volume-weighted across every tab — except the Cross-section views, which keep each code separate.",
-        "examples": [
-          "3801",
-          [
-            "0901",
-            "0902"
-          ],
-          "TOTAL"
-        ],
-        "title": "Product"
-      },
-      "remove_outliers": {
-        "default": true,
-        "description": "Drop extreme unit-price outliers before computing weighted-average prices.",
-        "title": "Remove Outliers",
-        "type": "boolean"
-      },
-      "reporter": {
-        "default": "European Union",
-        "description": "Declaring entity: an EU member state, an EU candidate country, Northern Ireland ('XI'), or one of the three aggregate presets ('European Union', 'Euro area', 'EU candidate countries'), or a predefined reporter group name.",
-        "title": "Reporter",
-        "type": "string"
-      },
-      "reporter_members": {
-        "anyOf": [
-          {
-            "items": {
-              "type": "string"
-            },
-            "type": "array"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "Explicit member countries for a custom reporter group. Each entry must be an EU member state, EU candidate country, or Northern Ireland. When more than one member is supplied the frame is aggregated into a synthetic group named after 'reporter'.",
-        "title": "Reporter Members"
-      }
-    },
-    "required": [
-      "product"
-    ],
-    "title": "DashboardQuery",
-    "type": "object"
-  }
-}

addedInput schema / additionalProperties
```
Added value: +false
```
removedInput schema / properties / query / $ref
```
Removed value: -"#/$defs/DashboardQuery"
```

addedInput schema / properties / query / properties

Added value: +{
+  "frequency": {
+    "default": "quarter",
+    "description": "Resampling frequency for the series: 'month', 'quarter' or 'year'.",
+    "type": "string"
+  },
+  "include_other": {
+    "default": true,
+    "description": "Bundle entities outside the top-N into a single 'Other' bucket.",
+    "type": "boolean"
+  },
+  "lang": {
+    "default": "en",
+    "description": "Language for translated labels in the response (en, de, fr, es, it, ro).",
+    "type": "string"
+  },
+  "midpoint": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": null,
+    "description": "Split point 'YYYY-MM' for the Pattern Shifts tab: the window is cut in two here and the before/after change per entity is reported. Defaults to the middle of the period when omitted."
+  },
+  "n_top": {
+    "default": 7,
+    "description": "Number of top entities (by volume/value) to break out individually in charts.",
+    "type": "integer"
+  },
+  "partner_set": {
+    "default": "non-EU countries",
+    "description": "Named partner preset, e.g. 'non-EU countries', 'EU countries', 'all countries', or a predefined partner group.",
+    "type": "string"
+  },
+  "partners": {
+    "anyOf": [
+      {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": null,
+    "description": "Explicit partner-country list that overrides 'partner_set' when present."
+  },
+  "period_end": {
+    "description": "Inclusive end of the analysis window, ISO month 'YYYY-MM'. Defaults to roughly three months ago — the latest period Eurostat typically has fully reported.",
+    "type": "string"
+  },
+  "period_start": {
+    "default": "2015-01",
+    "description": "Inclusive start of the analysis window, ISO month 'YYYY-MM'.",
+    "type": "string"
+  },
+  "prodcom_code": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": null,
+    "description": "Specific PRODCOM dataset code to pin for the Net Import Reliance and Trade Intensity tabs, when a single CN code maps to several. Ignored elsewhere."
+  },
+  "product": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      }
+    ],
+    "description": "Combined Nomenclature customs code(s), 2–8 digits, or the literal 'TOTAL' meta-aggregate (all products combined). Pass a list to aggregate several codes: their volumes are summed and prices volume-weighted across every tab — except the Cross-section views, which keep each code separate.",
+    "examples": [
+      "3801",
+      [
+        "0901",
+        "0902"
+      ],
+      "TOTAL"
+    ]
+  },
+  "remove_outliers": {
+    "default": true,
+    "description": "Drop extreme unit-price outliers before computing weighted-average prices.",
+    "type": "boolean"
+  },
+  "reporter": {
+    "default": "European Union",
+    "description": "Declaring entity: an EU member state, an EU candidate country, Northern Ireland ('XI'), or one of the three aggregate presets ('European Union', 'Euro area', 'EU candidate countries'), or a predefined reporter group name.",
+    "type": "string"
+  },
+  "reporter_members": {
+    "anyOf": [
+      {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": null,
+    "description": "Explicit member countries for a custom reporter group. Each entry must be an EU member state, EU candidate country, or Northern Ireland. When more than one member is supplied the frame is aggregated into a synthetic group named after 'reporter'."
+  }
+}

addedInput schema / properties / query / required
```
Added value: +[
+  "product"
+]
```
addedInput schema / properties / query / type
```
Added value: +"object"
```

removedInput schema / title

Removed value: -"get_market_summaryArguments"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "type": "object"
+}

First observedJul 21, 2026

TDQS

A4.8/5.0

Behavior5/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It explains that every figure reflects the query exactly as given, that NIR is normalized to 'year' regardless of the requested frequency, and that NIR is omitted if the product lacks a PRODCOM mapping. It also fully describes the return structure, which is comprehensive for a read-only analytical tool.

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 longer than average but well-structured: it opens with the core purpose, then gives usage guidance, and finishes with a detailed return-structure breakdown. Each section adds value, and the bullet-style list under narrative_facts is readable. It could be slightly trimmed without losing information, but it is far from bloated.

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?

Despite the tool's complexity (nested query, multiple output components), the description is complete: it covers purpose, usage, behavioral nuances (NIR normalization/omission), return fields, and how to adjust parameters. It even explains the tool's relationship to sibling tools. An agent has everything needed to select and invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema already documents all parameters at 100% coverage, so the baseline is 3. However, the description adds practical, tool-specific semantics: it recommends setting query.frequency to 'year' for multi-year summaries and explains that changing query.partner_set is the way to contrast different partner groups. These are meaningful usage insights beyond the schema's generic field descriptions.

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's function as a 'Report-section helper' that produces a 'condensed, report-ready digest of how a market has evolved', and it explicitly differentiates itself from the siblings get_overview, get_reporter_detail, get_concentration, and get_net_import_reliance by saying it replaces the need to call them separately. It is a specific verb+resource with clear scope.

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?

The description gives clear when-to-use guidance: for the 'General overview' report section, and recommends setting query.frequency to 'year' for multi-year evolution. It also provides an alternative usage path by telling the agent to call again with a different query.partner_set for different slices, explicitly stating it does not substitute a different reporter/partner_set. This is more than a generic usage context.

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

All EU Trade Explorer 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?