Skip to main content
Glama

finwire.pl - Polish financial data

GDP per capita and GDP growth in EU countries (Eurostat)

get_eu_gdp
Read-onlyIdempotent

Use for GDP per capita of EU countries, Poland against the EU in purchasing power, GDP growth of EU countries in a quarter, and when Poland could reach the EU average or another country. Tell the user that the catch-up year is arithmetic, not a forecast. GDP per capita of the 27 EU countries in purchasing power standards (PPS, EU27 = 100) and in EUR per inhabitant with the rank, real growth of GDP per capita (last year, 5- and 10-year averages), actual individual consumption per capita (AIC, EU27 = 100) and the price level of consumption, the latest quarter of real GDP growth (seasonally adjusted, quarter on quarter and year on year), the EU and the euro area, yearly history since 1995 of Poland, the EU and one country, and the finwire index finwire_eu_convergence_years (Licznik doganiania UE finwire): years until GDP per capita of Poland in PPS reaches the EU average at the average real growth of the last 10 years. Arithmetic on a constant pace, not a forecast.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_eu_gdp"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryNoEU country code (Eurostat, Greece = EL), e.g. DE. Adds this country to the answer and the history. Default DE.

Output Schema

NameRequiredDescriptionDefault
urlYes
asOfNo
dataNo
titleYes
sourceYes
docsUrlYes
licenseYes
summaryYes
citationYes
datasetIdYes
sourceUrlNo
truncatedNo
serverDateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely useful context beyond that: the catch-up year is arithmetic on a constant growth pace and must be presented to the user as such, not as a forecast. It does not discuss data freshness or revision behavior of Eurostat figures, which keeps it from a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Usage guidance is correctly front-loaded, but the second sentence is a single sprawling enumeration of every data series returned, and the arithmetic-not-a-forecast caveat is stated twice in slightly different words. Much of the returned-field enumeration duplicates what the output schema already provides.

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?

With an output schema present, the tool is fully specified: the agent knows what it returns, what the parameter does, and the key interpretive caveat about the convergence index. The only shortfall is bloat from re-describing return values the output schema already covers.

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?

There is a single optional parameter and the schema already documents the country code format, the Greece=EL quirk, and the DE default at 100% coverage. The description reinforces this by stating the yearly history covers Poland, the EU and "one country," which clarifies the parameter's additive effect on the history output.

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 names a concrete resource and scope: GDP per capita of the 27 EU countries in PPS and EUR, real GDP per capita growth, AIC, price level, quarterly real GDP growth, and the finwire_eu_convergence_years catch-up index. It is unmistakable against siblings such as get_eu_inflation or get_eu_earnings, which cover different indicators.

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?

"Use for GDP per capita of EU countries, Poland against the EU in purchasing power, GDP growth of EU countries in a quarter, and when Poland could reach the EU average" gives explicit trigger scenarios, including a question-shaped case (catch-up timing). It stops short of naming when-not-to-use or a specific alternative sibling for overlapping questions, so it is clear but not fully routing.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.