Skip to main content
Glama
Sign In
APIbase

APIbase

by whiteknightonhorse
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

EU HICP Annual Inflation

finance.eurostat.inflation
Read-onlyIdempotent

Retrieve monthly HICP annual inflation rate for an EU country from Eurostat. Specify country code and optional date range.

Instructions

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

Input Schema

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

Output Schema

NameRequiredDescriptionDefault
errorNoPresent only when the call failed. Includes error code, message, request_id, and any provider-specific extras.
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already indicate read-only, idempotent, non-destructive behavior. The description adds context about the metric (annual rate of change) and dataset, which is useful but 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?

The description is a single sentence plus dataset attribution, front-loading the key action and resource. No 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?

Given an output schema exists, the description adequately covers purpose, dataset, and licensing. It could mention default behavior or missing data handling, but is generally sufficient 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?

Schema coverage is 100%, so parameters are well-documented. The description reinforces the country parameter but adds no new semantic information 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 clearly states it provides 'Monthly HICP annual rate of change (overall index) for one EU country', specifying the dataset and license. This distinguishes it from sibling tools like GDP growth or unemployment.

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 use for inflation data but does not explicitly guide when to choose this tool over alternatives like other eurostat tools. No exclusions or comparisons are provided.

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

Deploy Server

Other Tools