Skip to main content
Glama

Openholidays

by io.github.pipeworx-io

School Holidays

school_holidays
Read-onlyIdempotent

School holidays (term breaks: Christmas, Easter, summer, etc.) for a European country in a date range, optionally scoped to one subdivision. This is the unique value-add over worldwide public-holiday sources — school calendars vary by region. EUROPE-focused (~30 countries). Returns each break with its localized name, dates, and observing subdivisions. Keyless.

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.
subdivision_codeNoOptional subdivision/region code to filter to, e.g. "DE-BY" (Bavaria). Use list_subdivisions to discover codes.

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": "CH",
+    "language": "de",
+    "subdivision_code": "CH-ZH",
+    "valid_from": "2024-06-01",
+    "valid_to": "2024-09-30"
+  }
+]
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already indicate read-only, open-world, idempotent, and non-destructive behavior. The description adds that returns include localized name, dates, and observing subdivisions, and states it is keyless, providing useful behavioral context beyond the annotations.

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?

The description is two sentences, front-loaded with the core purpose, and contains no fluff. Every sentence adds value.

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?

The tool has no output schema, but the description specifies return format (each break with localized name, dates, observing subdivisions). It also covers scope (Europe, ~30 countries), keyless access, and optional subdivision filtering, making it self-contained and informative.

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%, so each parameter is already described. The description reinforces the purpose of parameters (e.g., country is ISO code, subdivision is optional) and adds context about the European focus, aiding understanding of parameter usage.

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 returns school holidays (term breaks) for European countries in a date range, optionally scoped to a subdivision. It explicitly distinguishes itself from public holiday sources, which is a key differentiator from sibling tool 'public_holidays'.

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 provides clear context on when to use this tool (when school holiday data is needed, as opposed to public holidays) and its European scope. However, it does not explicitly state when not to use it or mention alternative tools by name, though 'public_holidays' is a sibling.

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