FREE. Catalog of all euroref reference-data series: supported countries, series ids, descriptions, freshness metadata and per-series URLs. Call this first to discover what data exists.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided. Description discloses it's a catalog (read-only list) but lacks details on permissions, rate limits, or side effects. The 'FREE' note adds minor context.
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 concise sentences; each adds value. First enumerates contents, second gives usage guidance. No fluff.
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?
Given zero parameters and no output schema, the description fully explains what the tool returns and its purpose. Sibling tools provide complementary operations, making this complete.
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?
No parameters, so description cannot add parameter info. Schema coverage is 100%, baseline 4 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 catalogs all euroref reference-data series with specific contents. Distinguished from sibling 'get_series' by being the discovery tool, explicit 'Call this first'.
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?
Explicitly says to call this first to discover data, implying sequential use. No explicit when-not but context is sufficient.
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 operation: minimum wage, income tax, VAT, working days, holidays, series data, and settlement dates. No overlap in purpose.
All tool names follow a consistent verb_noun pattern (e.g., check_minimum_wage, compute_income_tax, get_public_holidays, list_series). Only 'settlement_date' is a noun phrase but still clear.
10 tools cover a well-scoped domain of economic reference data without bloat. The count feels appropriate for the server's purpose.
Covers core areas: wage, tax, VAT, holidays, series, settlement dates. Minor gaps exist (e.g., no social security or currency data), but the scope is clearly defined and noted.
