Skip to main content
Glama

Paņem brīvdienu

latvia_calendar_statistics

Read-onlyIdempotent

Count working days, weekend days, holidays, total days off and working hours in 2026 or 2027 for a Monday-to-Friday week. Use it for yearly totals, such as how many working days or hours a year has; months gives each month's working days, working hours (a day before a holiday is one hour shorter), weekday_holidays (holidays that fall on a weekday) and pre-holiday dates; for the holiday dates use latvia_holidays, and for leave suggestions use latvia_plan_time_off. year must be 2026 or 2027. apply_transfers=true (2026 only) moves working days and days off as the 2026 transfers do, which bind only specified state-funded institutions; the moved counts are then non-zero.

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_calendar_statistics"
  }
}

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
monthsYes
holidaysYes
total_daysYes
weekend_daysYes
working_daysYes
working_hoursYes
moved_days_offYes
total_days_offYes
transfers_appliedYes
moved_working_daysYes

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 a read-only, idempotent, closed-world read, so the description focuses on non-obvious semantics: the year is restricted to 2026/2027, a pre-holiday day counts one hour shorter, and apply_transfers only exists for 2026 and only binds specified state-funded institutions, producing non-zero moved counts. That transfer caveat is exactly the kind of behavior an agent could not infer from 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?

Purpose and the year constraint are front-loaded, and every clause carries information. It is one dense run-on sentence chain, though, so the mode/alternative routing would scan better as separate sentences.

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?

With only two parameters, full schema coverage, rich annotations, and an output schema to carry return shapes, the description covers everything an agent needs: what is counted, which years are valid, what the transfer flag does, and which sibling handles adjacent tasks.

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 earns a step above by spelling out the effect of apply_transfers on the returned counts ('the moved counts are then non-zero') and by restating the year restriction in context. It stops short of adding any new syntax or format detail beyond the schema.

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?

The description names a specific resource and a specific set of computed metrics (working days, weekend days, holidays, days off, working hours) and scopes them to a Monday-to-Friday year view. It also explicitly distinguishes itself from siblings by naming latvia_holidays and latvia_plan_time_off for their respective jobs.

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?

It states exactly when to use this tool ('yearly totals'), what the alternate modes give (per-month working days/hours, weekday_holidays, pre-holiday dates), and routes the agent elsewhere for holiday dates and leave planning. Exclusions and alternatives are both explicit.

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