Skip to main content
Glama

Paņem brīvdienu

latvia_plan_time_off

Read-onlyIdempotent

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

NameRequiredDescriptionDefault
yearYesyear to plan leave in: 2026 or 2027
pto_daysYesmost working days of leave one break may use, 1 to 100
extra_days_offNoextra days off such as ones the employer gives, YYYY-MM-DD in 2026 or 2027, at most 100
apply_transfersNoapply the 2026 workday transfers (2026 only)
employment_start_dateNoYYYY-MM-DD; no leave is planned before it (nor before today in Latvia)

Output Schema

NameRequiredDescriptionDefault
statisticsYes
opportunitiesYes
transfers_appliedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent/non-destructive annotations: it defines what qualifies as 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'), states the temporal floor (never before today in Latvia or employment_start_date), and gives the exact ranking tie-break order plus the efficiency metric.

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?

Front-loads purpose, then usage routing, then constraints, then ranking — a sensible order with no filler sentences. It is a dense wall of run-on clauses, and the pto_hours/7-hour detail is tangential to a planning tool, which keeps it off a 5.

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

Completeness5/5

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

For a five-parameter, deterministic planning tool with an output schema, everything an agent needs is present: ranking order, break eligibility rule, temporal bounds, and parameter intent. Return values need not be explained further given the output schema.

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

Parameters5/5

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

Schema coverage is 100%, so the baseline would be 3, but the description adds genuine semantics the schema lacks: pto_days is a per-break ceiling rather than an annual budget, extra_days_off lets breaks build on employer-granted days, and pto_hours is explained as 8-hour full-time with 7 hours on a pre-holiday day. It also pins year to 2026/2027 and apply_transfers to 2026 only in prose.

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?

Opens with a specific verb and fully bounded output: 'Suggest up to ten long breaks in 2026 or 2027, best first, where a few leave days bridge weekends and Latvian holidays.' It also names the two sibling tools it should not be confused with, so an agent can route correctly without opening any schema.

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

Usage Guidelines5/5

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

Explicitly states the decision this tool supports ('use it to decide when to take leave') and routes the two adjacent intents elsewhere: latvia_holidays for holiday dates alone and latvia_leave_entitlement for leave balance. It also pre-empts the most likely misuse by clarifying that pto_days is a per-break cap, 'not a yearly budget to split.'

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