latvia_plan_time_off
Suggest up to ten long breaks in 2026 or 2027, best first, where a few leave days bridge weekends and Latvian holidays. Use it to decide when to take leave; for the holiday dates alone use latvia_holidays, and for how much leave the user has use latvia_leave_entitlement. pto_days caps the working days of leave each break may use on its own; it is not a yearly budget to split. A break takes every working day between runs of days off and holds a holiday or other day off on a weekday, so a week that only joins two weekends is not listed. Leave is never planned before today in Latvia or before employment_start_date. extra_days_off adds days the employer gives, so breaks can build on them. Breaks rank by days off, then fewer leave days, then date; efficiency is days off per leave day. pto_hours is the working hours of leave, assuming a full-time 8-hour day; 7 hours on a pre-holiday day.
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": {
"year": "<year>",
"pto_days": "<pto_days>"
},
"name": "latvia_plan_time_off"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| year | Yes | year to plan leave in: 2026 or 2027 | |
| pto_days | Yes | most working days of leave one break may use, 1 to 100 | |
| extra_days_off | No | extra days off such as ones the employer gives, YYYY-MM-DD in 2026 or 2027, at most 100 | |
| apply_transfers | No | apply the 2026 workday transfers (2026 only) | |
| employment_start_date | No | YYYY-MM-DD; no leave is planned before it (nor before today in Latvia) |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| statistics | Yes | ||
| opportunities | Yes | ||
| transfers_applied | Yes |