Skip to main content
Glama

finwire.pl - Polish financial data

Inflation in EU countries (Eurostat HICP)

get_eu_inflation
Read-onlyIdempotent

Use for inflation in EU countries, the place of Poland in the EU and price growth since a year. For the CPI of Statistics Poland, use get_macro_indicator. Harmonised inflation (HICP, annual rate) in the 27 EU countries, the EU and the euro area from Eurostat, monthly since 2000: the latest month with Poland, ranking from the highest inflation, change vs the previous month, the place of Poland and the place a month and a year earlier, five components (core inflation, food, energy, services, industrial goods), price growth in every country since the same month of a chosen year (basket), the finwire index finwire_eu_inflation_gap (Polish HICP minus EU HICP, percentage points) and the euro area flash estimate when newer. With country: that country's monthly component history. HICP is the EU-comparable measure; for the national CPI of Statistics Poland use get_macro_indicator.

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_inflation"
  }
}

Input Schema

NameRequiredDescriptionDefault
sinceNoStart year of the basket (price growth since the same month of that year), default 2015.
compareNoEU country code added to the history next to Poland, default DE.
countryNoEU country code (Eurostat, Greece = EL) for its component history and place; default Poland.

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.4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, closed-world, so the safety bar is low; the description instead discloses what the payload contains – latest month, ranking, month-over-month change, Poland's place now and a month/year ago, five components, basket growth, the finwire_eu_inflation_gap index and the euro-area flash estimate. This is substantial behavioural context beyond the annotations, though the coverage window (monthly since 2000) is the main temporal constraint and only lightly flagged.

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?

Front-loaded with the use case, which is good, but the body is a single very long run-on sentence enumerating payload sections, and the get_macro_indicator redirection appears twice in near-identical wording. It is dense and readable but wastes space on repetition.

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 and annotations covering the safety profile, the description's job is to convey scope and content, which it does thoroughly (time range, geography, components, derived index). Only the temporal granularity/update cadence beyond 'monthly since 2000' and the role of `compare` are left implicit.

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?

Schema coverage is 100%, so the baseline is 3; the description pushes above it by explaining the effect of `country` ('that country's monthly component history') and describing `since` as the basket baseline year in prose. The `compare` parameter's role is only visible in the schema, not 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?

States the specific resource (Harmonised HICP annual inflation for the 27 EU countries, EU and euro area from Eurostat) and immediately contrasts it with the sibling get_macro_indicator for Polish national CPI. An agent can identify the tool's domain and measure without opening the schema.

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?

Explicitly routes the agent: 'Use for inflation in EU countries... For the CPI of Statistics Poland, use get_macro_indicator,' repeated at the end for the national-CPI case. The only gap is that no when-not scenario beyond the CPI alternative is given, but the boundary is unambiguous.

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.