Skip to main content
Glama

Paņem brīvdienu

latvia_holidays

Read-onlyIdempotent

List Latvia's public holidays in 2026 or 2027, sorted by date, each with its Latvian and English name. Use it when you need the dates themselves; for totals use latvia_calendar_statistics, and to turn holidays into long breaks use latvia_plan_time_off. year must be 2026 or 2027; any other year is an error. apply_transfers=true (2026 only) adds the moved days off, flagged is_moved_day. Set it only for staff of the state-funded institutions the transfers bind.

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>"
    },
    "name": "latvia_holidays"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYescalendar year: 2026 or 2027
apply_transfersNoapply the 2026 workday transfers (2026 only; they bind only specified state-funded institutions)

Output Schema

NameRequiredDescriptionDefault
yearYes
holidaysYes
transfers_appliedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds context annotations cannot: the valid year range with an error condition, that apply_transfers is 2026-only, that it is only for staff of the state-funded institutions the transfers bind, and that results gain an is_moved_day flag. This is rich behavioral disclosure beyond the structured fields.

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-loaded with the core purpose, then usage routing, then parameter constraints — a logical order with little waste. It is dense rather than bloated, though the apply_transfers wording partly overlaps the schema description.

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 no explanation, and annotations cover the safety profile. With purpose, alternatives, year constraints, and transfer semantics all stated, an agent has everything needed to invoke the tool 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 description coverage is 100%, so the baseline is 3, but the description adds real semantic value: the effect of apply_transfers (adds moved days off, flagged is_moved_day) and its audience restriction. It slightly repeats the schema's own wording on 2026-only/institutions, keeping it below a 5.

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 (list Latvia's public holidays), the scope (2026 or 2027), ordering (sorted by date), and the returned content (Latvian and English names). It also explicitly distinguishes itself from the siblings latvia_calendar_statistics and latvia_plan_time_off, 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?

Gives explicit when-to-use ('when you need the dates themselves') plus named alternatives for the other cases (totals -> latvia_calendar_statistics, long breaks -> latvia_plan_time_off). It also states hard constraints: year must be 2026 or 2027 and any other year is an error.

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