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

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

feiertage_next_holiday

Find the next German public holiday on or after a given date for a selected federal state or nationwide, defaulting to today and checking the following year if needed.

Instructions

The next public holiday on or after a date in one German state. from_date: YYYY-MM-DD (default: today). state: 2-letter code or NATIONAL (default NATIONAL). Looks into the next year if the current year has no holiday left.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "feiertage_next_holiday"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateNoNATIONAL
from_dateNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does reasonably well: it discloses the today default, the NATIONAL default, and the non-obvious rollover into the next year when the current year has no holidays left. It omits error behavior for invalid state codes and does not confirm that no state is written to.

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?

Short and front-loaded, with the core purpose first and parameter notes after. The mid-sentence line breaks fragment the prose slightly, but no sentence is wasted.

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?

For a two-parameter read tool with an output schema, this covers purpose, both parameter formats and defaults, and the main edge case. The remaining gap is validation guidance for state codes, which is minor given an output schema handles the return value.

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 0%, so the description must compensate, and it does: from_date is given an explicit YYYY-MM-DD format plus a today default, and state is described as a 2-letter code or NATIONAL with a NATIONAL default. It stops short of listing valid state codes, which feiertage_list_states presumably supplies.

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?

States a concrete verb and resource: returns the next public holiday on or after a given date, scoped to one German state. That is meaningfully distinct from list_holidays or holidays_between, though the description never names a sibling to reinforce the boundary, so an agent must infer the split with feiertage_is_holiday.

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 context is implied by the phrase 'next public holiday on or after a date', but there is no explicit when-to-use or when-not-to-use guidance and no pointer to alternatives for multi-holiday or between-dates queries. The rollover note is the only conditional behavior spelled out.

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