Skip to main content
Glama

reference-data

by dev.afriref

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.4/5.0
Behavior4/5

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

No annotations provided; description carries full burden. It discloses that the tool is free, uses official government sources, handles subdivisions with merging, and tags results. It does not cover rate limits or authentication, but for a free API this is reasonable.

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?

Single paragraph, front-loaded with key info (FREE, official). Every sentence adds value; no redundancy or fluff.

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?

With no output schema, the description explains the return includes government source, subdivisions field, and regional holiday tagging. It covers the tool's core function adequately for typical use, though it could detail the exact return format.

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 coverage is 100% with both parameters described. The description adds value by explaining the subdivision parameter's behavior (merging national and regional holidays, tagging) beyond the schema's basic field description.

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?

Description clearly states it provides the official public-holiday calendar for a supported country, with a specific verb ('get') and resource ('public-holiday calendar'). It is well-distinguished from sibling tools (tax, payroll, working days) which are unrelated.

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 includes usage context like 'FREE' and explains sub-national calendar behavior. It implies when to use (holiday lookups) vs alternatives (working days, taxes), though it doesn't explicitly state exclusions.

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.3/5.0
Disambiguation5/5

Each of the 11 tools addresses a clearly distinct operation: compliance checking, income tax, payroll, VAT, working days, holidays, series queries (current/history/snapshot/catalog), and settlement date. Even within the tax and calendar families, the descriptions precisely delineate boundaries, so there is no realistic risk of an agent selecting the wrong tool.

Naming Consistency4/5

The vast majority of tools follow a consistent verb_noun snake_case pattern (check_, compute_, get_, list_, count_). The only deviation is settlement_date, which is a noun phrase rather than verb_noun, but it is still clear and idiomatic. This single outlier prevents a perfect score.

Tool Count5/5

With 11 tools, the server is well-scoped for a reference-data domain covering statutory rates, calculations, calendars, and settlement conventions. Each tool has a distinct purpose and earns its place; the count is neither thin nor bloated.

Completeness4/5

The server provides strong coverage of its stated domain: statutory tax computations, payroll, minimum wage, VAT, holidays, working days, and settlement dates, plus a generic series API for extensibility. Minor gaps exist, such as payroll only supporting Nigeria and Kenya and no standalone social-security contributor, but the response descriptions explicitly disclose these limits, and the generic series endpoint provides a workaround for common lookups.

Resources