EU Trade Explorer

Get Concentration Compare

get_concentration_compare

Partner-concentration (HHI) compared across sub-products: one HHI line per sub-product rather than per flow, to see which sub-products drive a parent code's overall concentration.

Input Schema

TableJSON Schema

Name	Required	Description
`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.
`compact`	No	If true, condense long numeric time series (more than ~6 points -- typically monthly/quarterly windows or wide multi-partner/multi-period breakdowns) into summary statistics (first, last, min, max, mean, pct_change) instead of returning every data point. Leave false for full-fidelity series (e.g. to actually plot a chart); set true when you just need the headline trend and want to save context.
`n_subcodes`	No	Max number of sub-products to plot as separate HHI lines.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

TDQS

A3.9/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 burden. It discloses the key behavioral trait of producing one HHI line per sub-product, but does not mention other behavioral aspects such as data source, response structure, or any side effects. The output schema helps fill gaps, but the description alone is limited.

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, focused sentence that front-loads the core concept (HHI comparison across sub-products) and the key differentiator (line per sub-product). It is concise and every phrase contributes meaning, with no redundant content.

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?

While the output schema provides rich descriptions for all parameters, the description itself is minimal. It lacks guidance on when to use this tool versus siblings like get_concentration or get_concentration_map, and does not mention that the query body is shared with other endpoints (though the schema does). Given the tool's moderate complexity, the description is adequate but not complete.

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 baseline is 3. The description's phrase 'one HHI line per sub-product' adds little beyond what the n_subcodes parameter description already states ('Max number of sub-products to plot as separate HHI lines'). No additional parameter semantics are provided in the description.

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 the specific verb 'compared' and resource 'Partner-concentration (HHI) across sub-products', clearly distinguishing it from per-flow tools. It explicitly says 'one HHI line per sub-product rather than per flow' and the intended purpose 'to see which sub-products drive a parent code's overall concentration', which differentiates it from siblings like get_concentration.

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?

The description provides clear usage context by contrasting with per-flow analysis ('rather than per flow') and stating the goal of identifying which sub-products drive concentration. However, it does not explicitly name alternative tools or state when not to use this tool, so it does not fully meet the 'explicit alternatives' bar.

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

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0

Disambiguation4/5

Most tools have clearly distinct purposes, but several concentration-related tools (get_concentration, get_concentration_compare, get_concentration_map) and volatility-related tools (get_volatility, get_volatility_summary) could be confused without careful reading. The detailed descriptions help, but the boundaries are not always immediately obvious.

Naming Consistency4/5

The vast majority of tools follow a consistent get_ prefix pattern for data retrieval. A few exceptions (guidelines_for_a_*, resolve_product_code, search_codes, validate_code) deviate to signal different kinds of operations, which is sensible but breaks uniformity.

Tool Count2/5

With 37 tools, the server is heavily overloaded. Many tools are variations on the same analytical theme (e.g., multiple concentration and production tools) and could be consolidated or parameterized. This creates a steep learning curve and increases the chance of selecting the wrong tool.

Completeness5/5

The tool set comprehensively covers the trade-exploration workflow: product code resolution, hierarchical browsing, headline stats, partner/reporter detail, concentration, volatility, shocks, production metrics, and report generation. There are no obvious gaps or dead ends for its stated purpose.

Resources

Need Help?