Get ECB monetary data. M3 money supply for the Euro Area or TARGET2 interbank balance data. Returns the last 12 monthly observations.
| Name | Required | Description | Default |
|---|---|---|---|
| series | No | m3 (M3 money supply, default) or target2 (TARGET2 balances) | m3 |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist, so the description must carry all behavioral info. It discloses that the tool returns the last 12 monthly observations and can return two data types. However, it omits details like whether the operation is read-only (implied but not stated), error conditions, or data freshness. Adequate but not rich.
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?
Two sentences with no redundant words. The first sentence immediately states the purpose, and the second provides specifics. Perfectly concise and front-loaded.
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?
The tool is simple (one parameter, no output schema), but the description only partially explains the return format ('last 12 monthly observations'). Without an output schema, more detail on data structure (e.g., date format, value type) would improve completeness. Adequate for a simple tool but leaves ambiguity.
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 parameter descriptions already explaining 'm3' and 'target2'. The description reiterates these values without adding new meaning (e.g., units, date range). Baseline score applies as no additional semantics are provided.
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?
The description clearly states it retrieves ECB monetary data, specifying two distinct series (M3 money supply and TARGET2 balances). This directly differentiates it from sibling tools get_ecb_rates (interest rates) and get_eurostat_data (broader statistics).
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?
The description implies usage for monetary data but does not explicitly guide when to use this tool over the siblings. It lacks 'when-to-use' or 'when-not-to-use' statements, though the specific mention of 'monetary data' provides some context.
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.
Each tool targets a distinct category of European economic data: ECB exchange rates and interest rates, Eurostat statistics, and ECB monetary data. Descriptions clearly differentiate them, preventing confusion.
All three tools use a consistent 'get_' prefix followed by descriptive snake_case names (e.g., get_ecb_rates, get_eurostat_data), forming a predictable pattern.
With only 3 tools, the server is tightly scoped to European economic data. Each tool serves a clear purpose without unnecessary bloat, making it easy for agents to navigate.
The tool set covers key areas: exchange rates, macroeconomic indicators (GDP, inflation, unemployment), and monetary aggregates. Minor gaps exist (e.g., no tool for bond yields or historical exchange rate ranges), but core needs are met.