Skip to main content
Glama

Gexiro DACH Pulse & Alexa Voice Suite MCP

get_school_holidays_and_bridge_days

Get upcoming German school vacations (Schulferien) and statutory public holidays (Feiertage) with countdown in days.

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": "get_school_holidays_and_bridge_days"
  }
}

Input Schema

NameRequiredDescriptionDefault
bundeslandNoGerman state (e.g. Nordrhein-Westfalen, Bayern, Hessen)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It discloses one behavioral detail (results include a countdown in days) but says nothing about how far ahead it looks, whether holidays are nationwide or state-filtered by default, or what happens when bundesland is omitted.

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?

One tight sentence with the resource front-loaded and no filler. Every clause ('with countdown in days') contributes information.

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

Completeness3/5

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

For a simple single-parameter read tool with no output schema, the description covers the essentials but leaves two consequential gaps: the undefined 'bridge days' concept from the tool name and the default scope when bundesland is omitted. Adding either would make it complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% for the single optional bundesland parameter with concrete state examples, so the schema already does the work. The description adds no meaning about the parameter, including the important question of what the default behavior is when no state is given; baseline 3 applies.

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 description gives a specific verb and resource and even supplies the German terms (Schulferien, Feiertage), so an agent immediately knows the domain. However, the tool is named get_school_holidays_and_bridge_days yet the description never explains what 'bridge days' (Brückentage) are, leaving part of the tool's scope unstated.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no exclusions, and no routing to alternatives among the many sibling tools. 'Upcoming' implies a forward-looking window but the horizon and the conditions under which this tool is the right choice are left to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources