Skip to main content
Glama
io.github.mohammad-abbasi-sh/feiertage-mcp

io.github.mohammad-abbasi-sh/feiertage-mcp

feiertage_is_holiday

Check whether a date is a public holiday in a German federal state or nationwide and get the holiday name(s). Use it to validate dates for scheduling and planning.

Instructions

Is a date a public holiday in one German federal state? day: YYYY-MM-DD, e.g. 2026-12-25. state: 2-letter code or NATIONAL (default NATIONAL). Returns is_holiday plus the holiday name(s).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "day": "<day>"
    },
    "name": "feiertage_is_holiday"
  }
}

Input Schema

NameRequiredDescriptionDefault
dayYes
stateNoNATIONAL

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description must carry the behavioral burden. It does disclose the return shape (is_holiday plus holiday name(s)) and the default state scope, but says nothing about invalid state codes, unsupported years, or whether the underlying dataset is limited to German holidays only.

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?

Three short sentences, front-loaded with the core question, then parameter formats, then the return value. No filler and no repetition of the tool name.

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?

A simple two-parameter lookup with an output schema, so the description need not explain return values and is roughly right-sized. It omits the enumeration of valid state codes and error behavior, the only meaningful gaps.

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 description coverage is 0%, so the description is the only source of parameter meaning, and it delivers: exact date format with a worked example and the standard/2-letter-code convention with the NATIONAL default. The main gap is that no valid state codes or a pointer to feiertage_list_states are given, leaving the agent to guess legal values.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening question names a specific operation (boolean holiday check) on a specific resource (a date in a German federal state). It is clearly narrower than the list/between/next siblings, though it never explicitly names those siblings as alternatives.

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

Usage Guidelines3/5

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

Usage is implied: use for a single-date yes/no check, with NATIONAL as the default scope stated parenthetically. There is no explicit guidance on when to prefer feiertage_holidays_between or feiertage_next_holiday instead, so the agent must infer routing from sibling names.

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