Skip to main content
Glama

reference-data

by dev.latamref

get_public_holidays

FREE. Official public-holiday calendar for a supported country, including gazetted movable holidays, with the official government source cited. Some countries also carry sub-national calendars (e.g. the German Laender): the subdivisions field lists them, and passing subdivision (ISO 3166-2, e.g. 'DE-BY') returns the national calendar merged with that region's statutory days.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countryYesISO country code
subdivisionNoOptional ISO 3166-2 region code (e.g. 'DE-BY'). Returns national + that region's statutory holidays, each tagged national/regional. Omit for the national calendar.

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations provided, the description covers key behavioral traits: it is free, uses official sources, returns national and optionally regional calendars, and tags holidays. Missing details like rate limits or authentication, but overall informative.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise but contains all essential information in a single paragraph. It is well-structured, starting with the key feature (free) and then detailing the functionality. Slightly verbose with 'e.g.' examples, but overall efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema, the description lacks details on the exact response format. It mentions tagging but does not specify fields like holiday names, dates, etc. While adequate for a simple tool, more completeness would help.

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?

Although schema coverage is 100%, the description adds meaningful context: explains the subdivision parameter's ISO 3166-2 format, effect on output, and the existence of a 'subdivisions' field. This goes beyond the schema's minimal descriptions.

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 holiday calendars for supported countries, with explicit mention of official sources and sub-national support. This distinguishes it from sibling tools which focus on wage, tax, or workday calculations.

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?

The description explains when to use the tool (retrieving holiday calendars) and provides guidance on optional subdivision parameter usage. However, it does not explicitly state when not to use it or suggest alternatives.

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

All reference-data toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

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 operation: compliance check, tax computation, VAT breakdown, day counting, holiday retrieval, series value/history/snapshot, catalog listing, and settlement date calculation. Even where underlying data overlaps (e.g., minimum wage as a series), the outputs and use cases are clearly differentiated.

Naming Consistency4/5

Nine of ten tools follow a clear verb_noun pattern (check_minimum_wage, compute_income_tax, compute_vat, count_working_days, get_public_holidays, get_series, get_series_history, get_snapshot, list_series). The outlier is settlement_date, which uses a noun phrase rather than a verb-based name, though it remains unambiguous and readable.

Tool Count5/5

With 10 tools, the server is well-scoped for its reference-data purpose, covering tax, wages, holidays, working days, series discovery, and settlement dates. Each tool earns its place without redundancy or bloat.

Completeness5/5

The surface provides comprehensive coverage: discovery via list_series, current/historical data via get_series and get_series_history, a full snapshot, tax computations, wage compliance, public holidays, working day counts, and settlement date calculations. There are no obvious gaps or dead ends for the intended domain.

Resources