Calcgrid

Add Lithuania Working Days

add_lt_working_days

Read-onlyIdempotent

Use this when you need a deterministic Lithuania 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 lithuania 2026 Labour Code holiday facts with explicit mon_fri_planning or mon_sat_planning. Sixteen full-day statutory holidays; pre-holiday one-hour rules do not create additional rest. No weekend substitution or bridge is inferred. Required work_schedule selects a planning calendar, not a universal personal roster. Actual hours, pay, shifts, local/employer/sector/school/bank schedules, religious personal leave, legal deadlines and future years are not computed. What it computes: Adds or subtracts working dates in the explicitly selected Lithuania 2026 five-day or six-day planning workweek. Sixteen statutory holidays; conditional one-hour eve markers never add full-day rest. Example user requests: Add or subtract Lithuania working days around Restoration of the State is a statutory holiday. | Add or subtract Lithuania working days around August 14 shortening is not full-day rest. | Add or subtract Lithuania working days around Good Friday is not an Article 123 rest day. | Add or subtract Lithuania working days around Easter eve depends on selected workweek. Inputs: start_date (date); working_days (integer); work_schedule (enum). Complete JSON argument examples: {"start_date":"2026-01-01","working_days":0,"work_schedule":"mon_fri_planning"} | {"start_date":"2026-01-01","working_days":0,"work_schedule":"mon_sat_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, work_schedule, is_statutory_holiday, is_preholiday_rule_date, is_shortened_workday, statutory_shortening_hours, shortening_scope, working_hours_scope, personal_roster_scope, payroll_scope. Formula: planning_workday = day in selected workweek AND no statutory_holiday_rest; shortened work dates count once Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/lithuania-public-add-working-days with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/lithuania-public-add-working-days.md

Input Schema

TableJSON Schema

Name	Required	Description
`start_date`	Yes	Gregorian start date in 2026-2026.
`working_days`	Yes	Signed offset; start date excluded for non-zero offsets.
`work_schedule`	Yes	Required mon_fri_planning or mon_sat_planning. Choose the intended baseline explicitly; no universal or personal roster inferred.

Output Schema

TableJSON Schema

Name	Required	Description
`links`	No
`result`	Yes
`request`	Yes
`sources`	No
`success`	Yes
`version`	No
`freshness`	No
`timestamp`	Yes
`next_actions`	No
`service_version`	Yes	Deployed Calcgrid implementation version used for the result.

Schema Changelog

Changes observed during successful MCP inspections.

AddedSep 29, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior. The description adds substantial context beyond those annotations: deterministic planning-calendar semantics, sixteen statutory holidays, no weekend substitution or bridge inference, and explicit non-computation of payroll, personal leave, and future years.

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

Conciseness2/5

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

The description is far longer than necessary and includes redundant sections: a full output list despite an output schema, example user requests, and complete JSON examples already present in the schema. It is front-loaded but bloated with material that does not earn its place.

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?

Given the tool's complexity, the description is complete enough for correct invocation. It covers inputs, formula, holiday behavior, exclusions, REST fallback, and documentation link, and nothing essential is missing.

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. The description adds meaning through the planning formula and explicit notes that work_schedule selects a planning calendar rather than a personal roster, though the JSON examples largely duplicate the schema examples.

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 states a specific verb and resource: 'Adds or subtracts working dates' for Lithuania. It distinguishes the tool from sibling check_lt and count_lt tools by framing it as an offset calculation, and it names the country and year scope directly.

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?

It gives clear when-to-use guidance and several when-not-to-use exclusions, such as actual hours, pay, shifts, and personal rosters. The awkward 'Do not use this when lithuania 2026 Labour Code holiday facts...' sentence is unclear, and it does not explicitly name sibling alternatives like check_lt or count_lt.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Calcgrid tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?