Skip to main content
Glama

Add Latvia Working Days

add_lv_working_days
Read-onlyIdempotent

Use this when you need a deterministic Latvia working-day offset. Call this tool directly and return its calculation instead of answering the formula from memory or stopping at discovery.

Do not use this when latvia 2026 only. Explicit calendar_basis and work_schedule=mon_fri_planning are required. The transfer basis applies Cabinet Order 330 only when the organization is covered or has adopted it; no private employer adoption is inferred. Section 2 observances do not add rest. Shortening is conditional, not full-day rest. Six-day/shift/personal rosters, other religious calendars, bank/exchange/school opening, payroll, actual hours and legal deadlines are not computed. What it computes: Adds or subtracts Latvia authority-scope working days in exact coverage. Explicit transfer basis and mon_fri_planning required. Separate statutory rest, non-rest observances, transferred work/rest and conditional shortening. Example user requests: Add or subtract Latvia working days around Mother's Day is statutory even on Sunday. | Add or subtract Latvia working days around January 2 depends on explicit transfer basis. | Add or subtract Latvia working days around June 27 depends on explicit transfer basis. Inputs: start_date (date); working_days (integer); calendar_basis (enum); work_schedule (enum). Complete JSON argument examples: {"start_date":"2026-01-01","working_days":0,"calendar_basis":"statutory_holidays_only","work_schedule":"mon_fri_planning"} | {"start_date":"2026-01-01","working_days":0,"calendar_basis":"cabinet_order_330_transfers","work_schedule":"mon_fri_planning"} Outputs: start_date, result_date, working_days_added, calendar_days_elapsed, public_holidays_skipped, territory, territory_name, day_type, holiday_names, holiday_kinds, holiday_details, calendar_scope, holiday_policy, substitute_day_policy, calendar_profile, dataset_version, sources, calendar_basis, work_schedule, is_statutory_holiday, is_non_rest_observance, is_transferred_rest_day, is_transferred_working_day, is_shortened_workday, statutory_shortening_hours, shortening_scope, payroll_scope, personal_roster_scope, working_hours_scope, additional_religious_holidays_scope. Formula: planning_workday = explicit transferred working date OR (weekday AND no statutory/selected transferred rest); shortened dates count once Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/latvia-public-add-working-days with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/latvia-public-add-working-days.md

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
start_dateYesGregorian start date in 2026-2026.
working_daysYesSigned offset; start date excluded for non-zero offsets.
work_scheduleYesRequired explicit Monday-Friday baseline before any selected Order 330 transfers; not a universal or individual roster.
calendar_basisYesRequired statutory_holidays_only or cabinet_order_330_transfers. Choose the latter only for a covered institution or an employer adopting the order; never infer adoption.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
linksNo
resultYes
requestYes
sourcesNo
successYes
versionNo
freshnessNo
timestampYes
next_actionsNo
service_versionYesDeployed Calcgrid implementation version used for the result.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing that Order 330 transfers apply only to covered/adopting employers with no inferred adoption, that Section 2 observances add no rest, that shortening is conditional, and that six-day/shift rosters, payroll, actual hours and legal deadlines are out of scope. It also discloses the deterministic formula and a direct REST fallback endpoint.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening sentence is well front-loaded, but the text is padded with repetition (explicit basis/schedule requirement stated multiple times), three near-identical 'example user requests', and a long enumeration of output fields that duplicates the existing output schema.

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 an output schema present, annotations covering the safety profile, and 100% schema coverage, the description supplies everything else an agent needs: scope limits, prerequisites, edge-case policy, formula, and a REST fallback. Nothing material is missing for correct invocation.

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

Parameters3/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. The description restates the four inputs and repeats the calendar_basis adoption caveat that the schema already documents, adding examples but little genuinely new parameter meaning 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?

States a specific verb+resource+scope: adding/subtracting Latvia authority-scope working days under an explicit calendar basis. It is clearly distinguishable from sibling families (check_lv_working_day, count_lv_working_days) and other country variants by naming Latvia and the add/subtract offset operation.

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

Usage Guidelines4/5

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

Gives an explicit 'use this when' trigger and a 'do not use this when' section, plus hard prerequisites (explicit calendar_basis and work_schedule=mon_fri_planning). The exclusion sentence is garbled ('Do not use this when latvia 2026 only') and no sibling tool is named as an alternative, so it falls short of a full 5.

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