Skip to main content
Glama

Paņem brīvdienu

latvia_leave_entitlement

Read-onlyIdempotent

Estimate annual paid leave under the Latvian Labour Law, in calendar days excluding public holidays. Use it to answer how much leave someone has in a year; to find when to take it use latvia_plan_time_off, which counts leave in working days, a different unit. Pass annual_base=28 (the legal minimum) unless the contract grants more, and fte_percentage=1 for full time; part-time work does not shorten leave. birth_date matters only for employees under 18, who get one calendar month. If employment_start_date is on or after 1 January of year, the result is an accrual estimate; the full leave may be requested after six months of work.

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": {
      "employment_start_date": "<employment_start_date>",
      "year": "<year>",
      "fte_percentage": "<fte_percentage>",
      "annual_base": "<annual_base>"
    },
    "name": "latvia_leave_entitlement"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYesyear to estimate, 2020 to 2100
birth_dateNoYYYY-MM-DD; employees under 18 get one calendar month
annual_baseYesannual leave in calendar days, 28 (the legal minimum) to 60
fte_percentageYesworking time as a fraction of full time, 0.1 to 1.0 (part-time work does not shorten leave)
employment_start_dateYesYYYY-MM-DD

Output Schema

NameRequiredDescriptionDefault
unitYes
base_usedYes
is_under_18Yes
entitlement_daysYes
is_accrual_estimateYes
under_18_calendar_monthYes
six_month_threshold_reached_by_year_endYes

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?

Annotations already declare readOnly, idempotent, non-destructive, so safety is covered; the description adds substantive domain behavior beyond them: leave counted in calendar days excluding public holidays, part-time work not shortening leave, the under-18 one-calendar-month rule, and the accrual caveat for starts on/after 1 January (full leave only after six months).

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?

Four dense sentences, front-loaded with purpose and unit, then the sibling disambiguation, then parameter defaults, then the accrual caveat. No filler sentences and nothing repeated from the schema or annotations.

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?

An output schema exists, so return values need not be explained. Given a read-only estimator with five parameters, full schema coverage, and explicit sibling routing plus domain rules, an agent has everything needed to select and invoke it correctly.

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 100%, so the baseline is 3. The description goes further by giving decision guidance the schema lacks: which value to pass for annual_base and why (legal minimum vs contract), what fte_percentage=1 means, and the fact that birth_date only matters for under-18s while employment_start_date governs accrual.

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 and resource ('Estimate annual paid leave under the Latvian Labour Law') and pins the unit precisely ('calendar days excluding public holidays'). It also names the sibling latvia_plan_time_off and the exact difference (working days, a different unit), so an agent can disambiguate without opening either 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 says when to use it ('to answer how much leave someone has in a year') versus when to use the alternative ('to find when to take it use latvia_plan_time_off'), and it names the selecting condition. It further supplies invocation defaults (annual_base=28 unless the contract grants more, fte_percentage=1) and states the accrual condition tied to employment_start_date.

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