Skip to main content
Glama

EU HICP Annual Inflation

finance.eurostat.inflation
Read-onlyIdempotent

Get the monthly HICP annual inflation rate for EU countries or aggregates using Eurostat data. Specify country, start and end periods to analyze price stability.

Instructions

Monthly HICP annual rate of change (overall index) for one EU country. Eurostat dataset prc_hicp_manr, CC BY 4.0

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countryNoEurostat geo code — 2-letter country (DE, FR, IT, ES, UK, PL, ...) or aggregate ("EU27_2020", "EA20"). One country per call. Default: "EU27_2020".
sinceNoEarliest period to return — format depends on series frequency: "2020" (annual), "2024-01" (monthly), "2024Q1" (quarterly).
untilNoLatest period to return — same format as `since`.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultNoTool response payload. Shape varies per tool — consult the tool description and inputSchema. May be an object, array, string, or number depending on the upstream provider response.
errorNoPresent only when the call failed. Includes error code, message, request_id, and any provider-specific extras.
Behavior3/5

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

Annotations already declare readOnly, idempotent, and openWorld hints. The description adds dataset attribution but no additional behavioral context (e.g., rate limits, pagination). It does not contradict annotations.

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?

Single, front-loaded sentence conveys purpose, dataset, and license without any wasted words.

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 annotations covering safety and output schema present, the description is mostly complete. It could add context about the returned time series, but is adequate for a simple retrieval tool.

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?

Input schema has 100% coverage of parameter descriptions. The description adds no extra meaning beyond the schema, earning the baseline score.

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 monthly HICP annual rate of change for one EU country, specifying the dataset and license. It distinguishes itself from sibling tools that cover different Eurostat indicators.

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?

The description implies one country per call but does not explicitly state when to use this tool versus alternatives like other Eurostat tools. No guidance on prerequisites or exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/whiteknightonhorse/APIbase'

If you have feedback or need assistance with the MCP directory API, please join our Discord server