ecb_hicp_inflationHarmonised Index of Consumer Prices (HICP) annual rate of change for a country / euro area. Monthly frequency. country defaults to U2 (euro area).
| Name | Required | Description | Default |
|---|---|---|---|
| country | No | Reference area — U2 (euro area, default), DE, FR, IT, ES, NL, BE, etc. | |
| end_period | No | End date (YYYY or YYYY-MM) | |
| start_period | No | Start date (YYYY or YYYY-MM) |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Input schema / examplesAdded value: +[
+ {
+ "country": "U2"
+ },
+ {
+ "country": "DE",
+ "end_period": "2024-01",
+ "start_period": "2023-01"
+ }
+]Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, etc. Description adds default country and frequency, but does not deepen behavioral understanding beyond annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Single, well-structured sentence with key information (what, frequency, default) front-loaded. No wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple read-only tool with three well-described parameters and no output schema, the description is sufficiently complete. Could optionally mention data format or limitations, but not required.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with descriptions for all parameters. Description adds only the default value for 'country', which is useful but not transformative. Baseline of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states it retrieves the HICP annual rate of change for a country/euro area, with monthly frequency and default country. Distinguishes from sibling ECB tools.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No explicit when/when-not or alternative tool mention, but the name and description clearly indicate it is for HICP inflation data, making usage obvious.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.