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

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

feiertage_holidays_between

List German public holidays between two dates for a selected federal state or nationwide, helping you plan schedules and check holiday coverage.

Instructions

Public holidays in a date range in one German federal state. start_date / end_date: YYYY-MM-DD (max range ~2 years). state: 2-letter code or NATIONAL (default NATIONAL).

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": {
      "start_date": "<start_date>",
      "end_date": "<end_date>"
    },
    "name": "feiertage_holidays_between"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateNoNATIONAL
end_dateYes
start_dateYes

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?

With no annotations, the description carries the full burden, and it does disclose two genuinely useful constraints: the ~2-year maximum range and the NATIONAL default. It omits the safety profile (trivially a read) and any note on ordering or pagination, but the range limit is the error-causing behavior an agent most needs.

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 lines with the core purpose front-loaded and parameters itemized below; no filler, no restatement of the tool name. Every line carries information the agent needs.

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?

An output schema exists, so return-value explanation is not required, and all three parameters are documented despite zero schema coverage. The only substantive omission is where the valid state codes come from, which matters for a tool whose main optional input is a coded jurisdiction.

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 largely does: both dates get an explicit YYYY-MM-DD format, state gets a format (2-letter code) and a documented default. The remaining gap is that no valid state codes are enumerated or cross-referenced, leaving the agent to guess the accepted 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 first line names a specific resource (public holidays), a scope (date range), and a jurisdiction (one German federal state), which cleanly separates it from siblings like is_holiday or next_holiday. The verb is only implied by the tool name, not stated in the description, but the scope statement is precise enough to select on.

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 by the range framing, and the documented ~2-year max plus the NATIONAL default tell the agent how to call it. However, there is no explicit routing guidance — nothing says to use feiertage_list_states to discover valid state codes, or that feiertage_is_holiday covers single-date checks.

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