Skip to main content
Glama

Inflation rate by country and month

get_inflation
Read-onlyIdempotent

Annual inflation rate (HICP, Eurostat) of one European country, the euro area or the EU in one month, with core, energy, food and services inflation for the same month. Without a month it returns the latest published month and says whether that figure is still a flash estimate. Monthly, up to 20 years back.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "country": "<country>"
    },
    "name": "get_inflation"
  }
}

Input Schema

NameRequiredDescriptionDefault
monthNoMonth as YYYY-MM. Omit for the latest published month.
countryYesISO 3166-1 alpha-2 country code (Greece is GR), or EA for the euro area, or EU for the European Union

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real behavior beyond that: a default resolution path when month is omitted, the flash-estimate flag on the latest figure, the 20-year history bound, and the fact that component series come back alongside the headline rate. It stops short of stating units (percent) or the response shape.

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?

Three tight sentences with zero filler: the resource and its components come first, the no-month default second, the temporal scope last. Every sentence carries distinct information and none restates the tool name.

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 no output schema, the description carries the burden of explaining returns, and it does name the headline series, the four component series and the flash-estimate indicator. It leaves the numeric representation (percentage points, precision) and any response envelope unstated, which is a modest gap for a two-parameter read 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?

Schema coverage is 100%, with patterns, enum values and per-parameter descriptions already in place, so the baseline is 3. The description contributes the single-country semantics of the country parameter (one at a time, not a list) and the default-and-flag behavior of month, but adds no formatting or value details beyond the schema.

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 specific verb+resource pairing: annual inflation rate (HICP, Eurostat) for exactly one country, EA or EU, in one month, plus the four sub-components (core, energy, food, services). It also pins the data source and the time window, so an agent can distinguish it from siblings like get_ecb_rates or get_wages 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It clearly states the context for omitting the month ('returns the latest published month and says whether that figure is still a flash estimate') and the coverage limit ('monthly, up to 20 years back'). What is missing is explicit routing: it never says to use compare_countries when more than one country is needed, even though the 'one country' constraint implies it.

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.

Resources