io.github.mohammad-abbasi-sh/ecb-mcp

ecb_inflation

Retrieves HICP annual inflation rates for the euro area or Germany over a chosen number of recent months, enabling inflation trend checks.

Instructions

HICP annual inflation rate (%). area: "U2" (euro area, default) or "DE" (Germany). limit: 1..24 months (default 6).

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": "ecb_inflation"
  }
}

Input Schema

Name	Required	Description	Default
`area`	No		U2
`limit`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 13, 2026

TDQS

B3.4/5.0

Behavior2/5

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

No annotations exist, so the description carries the full disclosure burden, and it discloses almost no behavior: no data source, refresh cadence, series vintage, or whether values are seasonally adjusted. It only hints at monthly frequency via the 'months' wording in the limit parameter.

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

Conciseness4/5

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

Two compact clauses, metric and unit front-loaded, then the parameter facts. Slightly telegraphic, but no sentence is wasted.

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?

For a two-parameter read tool with an output schema already documenting return values, the description supplies the metric definition, the accepted area values, and the limit range. Only data frequency and source provenance are unstated.

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 0%, so the description must compensate, and it does: 'area' is given two concrete values with meanings (U2 = euro area default, DE = Germany) and 'limit' gets both a range (1..24) and a default. It does not say whether other country codes are accepted, which is the remaining ambiguity.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific metric and unit: HICP annual inflation rate in percent. The metric name itself separates it from siblings like ecb_bond_yields or ecb_money_supply, though the description never explicitly contrasts with them or uses a verb like 'retrieve'.

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?

Implies usage through parameter defaults (euro area, 6 months) but never says when to pick this over other ECB series or in what analytical context. It is adequate parameter context rather than true when-to-use guidance.

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

Deploy Server