get_holidays
Public holidays for an EU country and year (2026-2028), optionally narrowed to a German region (e.g. BY). 2 credits, requires an API key.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| year | Yes | ||
| region | No | ||
| country | Yes |
dropcoin-utility
TDQS
A4.4/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the burden. It discloses cost (2 credits) and authentication requirements (API key), which are non-obvious behavioral traits. It also clarifies the year restriction and German-region scoping. It does not describe response format, but for a simple lookup this is acceptable.
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?
A single sentence that front-loads the core purpose and adds essential operational details (credits, API key) without fluff. Every word earns its place.
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 3-parameter lookup tool with no output schema or annotations, the description covers purpose, scope, parameters, cost, and auth. It lacks response format information, but the tool's simplicity makes this a minor gap.
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 has no parameter descriptions (0% coverage), but the description adds meaning: country is an EU country, year is restricted to 2026-2028, and region is optional and specifically German. This goes beyond the raw schema patterns and enums.
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 the tool retrieves public holidays for an EU country and year, with optional German region filtering. This specific verb+resource combination distinguishes it from sibling tools like get_fx_rate or get_timezone.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Provides clear context: EU countries, year range (2026-2028), and optional German region. It does not explicitly mention alternatives or when not to use, but the purpose is self-evident relative to siblings.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A4.4/5.0
Disambiguation5/5
Each tool targets a distinct resource: FX rates, holidays, timezones, VAT rates, and IBAN validation. There is no functional overlap, so an agent can easily select the right tool for a task.
Naming Consistency5/5
All tool names follow a consistent <verb>_<noun> snake_case pattern: get_fx_rate, get_holidays, get_timezone, get_vat_rate, validate_iban. The verb varies but the style is uniform and predictable.
Tool Count5/5
Five tools is an appropriate scope for a utility server focused on EU-related data. Each tool provides a clear, non-redundant capability, and the count is neither too sparse nor overwhelming.
Completeness4/5
The set covers the key EU administrative and financial data points (FX, holidays, timezone, VAT, IBAN). A minor gap is the lack of a country metadata tool, but the existing tools cover core workflows without dead ends.