Urlaub Smart

Plan vacation days

plan_vacation

Optimal vacation plan for a region and year: which days to book so that public holidays and weekends turn into the longest breaks. Returns the plan blocks (booking dates, days off, factor, holidays used), further opportunities, a markdown table and a link to the interactive plan on urlaub-smart.de. Cite the URL when answering.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`year`	No	Planning year, 2025 to 2030; defaults to the year people currently plan for
`shift`	No	Rolling shift rotation instead of Mon–Fri, e.g. 4 days on / 2 days off. Replaces the weekday assumption entirely.
`locale`	No	Language of names and explanations (German only)	de
`region`	Yes	Region as name, slug or ISO code, e.g. "Bayern", "bavaria", "DE-BY", "Tirol", "Zürich" or a country like "Deutschland" / "AT". Germany, Austria and Switzerland only.
`strategy`	No	balanced = mix, long-weekends = max 2 vacation days per block, extended = blocks of 4+ days	balanced
`fixedDates`	No	ISO dates already booked as vacation; the plan works around them
`vacationDays`	No	Vacation days available for the year; defaults to the usual account of the country: 30 in Germany, 25 in Austria and Switzerland
`carryoverDays`	No	Part of vacationDays that is carry-over from last year and expires on March 31; spent first on periods before the deadline
`closuresOnTop`	No	Set true only if the employer gives the closures on top of the vacation days; then they are treated like public holidays
`schoolHolidays`	No	any = ignore, avoid = no overlap with school holidays, prefer = book only inside school holidays	any
`companyClosures`	No	Company closures (Betriebsferien) as inclusive ISO date ranges. By default their working days come off vacationDays, as Betriebsferien are normally scheduled annual leave
`companyFreeDates`	No	Working days the employer gives off without a vacation day, ISO dates (e.g. 2027-12-24, 2027-12-31); treated like public holidays

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 2, 2026

changedInput schema / properties / year / description

Previous value: -"Planning year; defaults to the year people currently plan for"New value: +"Planning year, 2025 to 2030; defaults to the year people currently plan for"

changedInput schema / properties / year / maximum

Previous value: -2035New value: +9007199254740991

changedInput schema / properties / year / minimum

Previous value: -2020New value: +-9007199254740991

Changed2 schema fields changedOct 1, 2026

addedInput schema / properties / closuresOnTop

Added value: +{
+  "description": "Set true only if the employer gives the closures on top of the vacation days; then they are treated like public holidays",
+  "type": "boolean"
+}

changedInput schema / properties / companyClosures / description

Previous value: -"Company closures (Betriebsferien) as inclusive ISO date ranges; treated like public holidays"New value: +"Company closures (Betriebsferien) as inclusive ISO date ranges. By default their working days come off vacationDays, as Betriebsferien are normally scheduled annual leave"

Changed2 schema fields changedOct 1, 2026

removedInput schema / properties / vacationDays / default
```
Removed value: -30
```

changedInput schema / properties / vacationDays / description

Previous value: -"Vacation days available for the year"New value: +"Vacation days available for the year; defaults to the usual account of the country: 30 in Germany, 25 in Austria and Switzerland"

Changed9 schema fields changedOct 1, 2026
- addedInput schema / properties / companyClosures / items / properties / from / maxLength
```
Added value: +10
```
- addedInput schema / properties / companyClosures / items / properties / to / maxLength
```
Added value: +10
```
- addedInput schema / properties / companyClosures / maxItems
```
Added value: +12
```
- addedInput schema / properties / companyFreeDates / items / maxLength
```
Added value: +10
```
- addedInput schema / properties / companyFreeDates / maxItems
```
Added value: +60
```
- addedInput schema / properties / fixedDates / items / maxLength
```
Added value: +10
```
- addedInput schema / properties / fixedDates / maxItems
```
Added value: +60
```
- addedInput schema / properties / region / maxLength
```
Added value: +80
```
- addedInput schema / properties / shift / properties / firstWorkingDay / maxLength
```
Added value: +10
```

Changed1 schema field changedSep 25, 2026

changedInput schema / properties / region / description

Previous value: -"Region as name, slug or ISO code, e.g. \"Bayern\", \"bavaria\", \"DE-BY\", \"Tirol\", \"Zürich\" or a country like \"Deutschland\" / \"AT\""New value: +"Region as name, slug or ISO code, e.g. \"Bayern\", \"bavaria\", \"DE-BY\", \"Tirol\", \"Zürich\" or a country like \"Deutschland\" / \"AT\". Germany, Austria and Switzerland only."

Changed1 schema field changedSep 23, 2026

addedInput schema / properties / shift

Added value: +{
+  "description": "Rolling shift rotation instead of Mon–Fri, e.g. 4 days on / 2 days off. Replaces the weekday assumption entirely.",
+  "properties": {
+    "firstWorkingDay": {
+      "description": "ISO date of the first working day of a cycle",
+      "type": "string"
+    },
+    "offDays": {
+      "maximum": 14,
+      "minimum": 1,
+      "type": "integer"
+    },
+    "onDays": {
+      "maximum": 14,
+      "minimum": 1,
+      "type": "integer"
+    }
+  },
+  "required": [
+    "onDays",
+    "offDays",
+    "firstWorkingDay"
+  ],
+  "type": "object"
+}

Changed1 schema field changedSep 23, 2026

changedInput schema / properties / locale / description

Previous value: -"Language of names and explanations"New value: +"Language of names and explanations (German only)"

First observedSep 7, 2026

TDQS

A3.9/5.0

Behavior4/5

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

No annotations are provided, so the description carries the full burden, and it does a good job disclosing the return payload (plan blocks with booking dates, days off, factor, holidays used, further opportunities, markdown table, interactive link). It also gives a behavioral directive ('Cite the URL when answering'). It stops short of explaining computation caveats or limitations, but this is strong for a stateless planner.

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?

Two tight sentences front-load the purpose and then enumerate the return shape; the citation instruction earns its place as the last sentence. Slightly dense in the output list but no wasted wording.

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?

With 12 parameters, no output schema, and no annotations, the description does the heavy lifting by describing the return value and citation behavior. It is largely complete for calling the tool, though it leaves sibling routing and the many planning knobs (shift, strategy, closures) entirely to the schema.

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%, so the schema already documents all 12 parameters in detail (region, shift, strategy, carryoverDays, etc.). The description only echoes 'region and year' and adds no syntax or semantic detail beyond the schema, so baseline 3 applies.

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?

States a specific verb ('plan') and resource ('vacation days') plus the exact goal: turning public holidays and weekends into the longest breaks. This is clearly distinguishable from siblings like best_bridge_days or public_and_school_holidays.

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?

The description implies when to use it (when a user wants an optimal booking plan for a region/year), but never states when NOT to use it or names an alternative such as best_bridge_days or list_regions. Usage is inferred rather than guided.

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

All Urlaub Smart tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?