Skip to main content
Glama

Openholidays

by io.github.pipeworx-io

Public Holidays

public_holidays
Read-onlyIdempotent

Public (statutory) holidays for a European country in a date range, with regional subdivisions. EUROPE-focused (~30 countries: DE, FR, NL, CH, IT, AT, BE, ES, PL, etc.). Returns each holiday with its localized name, dates, whether it is nationwide, and which subdivisions observe it. Keyless. For school terms/breaks use school_holidays instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countryYesISO 3166-1 alpha-2 country code, e.g. "DE", "FR", "NL", "CH", "IT".
languageNoLanguage for names, ISO 639-1 (default "EN").
valid_toYesEnd of date range, YYYY-MM-DD.
valid_fromYesStart of date range, YYYY-MM-DD.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "country": "DE",
+    "valid_from": "2024-01-01",
+    "valid_to": "2024-12-31"
+  },
+  {
+    "country": "FR",
+    "language": "fr",
+    "valid_from": "2024-04-01",
+    "valid_to": "2024-06-30"
+  }
+]
  2. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive. Description adds that it is keyless, returns localized names, dates, nationwide status, and subdivisions. No contradictions.

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?

Two sentences, front-loaded with key information. Every word adds value. No redundancy.

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

Completeness5/5

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

Despite no output schema, description explains return structure (localized name, dates, nationwide, subdivisions). Complete for a read-only retrieval tool with good annotations.

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 100% (all parameters described). Description adds context: country code format, language default (EN), and examples. Provides extra value beyond schema.

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?

Clearly states it returns public holidays for European countries in a date range with regional subdivisions. Specific verb 'returns' and resource 'public (statutory) holidays'. Distinguishes from sibling tool school_holidays.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly specifies EUROPE-focused (~30 countries with examples), and instructs when to use school_holidays instead. Provides clear context for when to use this tool versus alternatives.

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

All Openholidays 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

A3.8/5.0
Disambiguation2/5

Several tools have overlapping purposes (e.g., ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded; multiple Polymarket tools) and many serve unrelated domains, making it hard for an agent to distinguish which tool to use for a given task, especially given the server's holiday theme.

Naming Consistency3/5

Most tool names follow a lowercase_with_underscores pattern, but the prefixes vary (ask_pipeworx, pipeworx_*, polymarket_*, etc.) and some names are less descriptive (e.g., process, run, execute-like vague verbs are absent, but still the naming lacks a unified convention across the broad set.

Tool Count2/5

35 tools is excessive for a server named 'Openholidays'. The vast majority of tools (e.g., SEC filings, Polymarket, npm scanning) are unrelated to holidays, making the tool count feel bloated and unfocused.

Completeness3/5

For the holiday domain, the server includes necessary tools (list_countries, list_subdivisions, public_holidays, school_holidays) and is complete. However, the server's actual scope is far broader, and many unrelated tools are present, which dilutes the completeness for its stated purpose.

Resources