add_lt_working_days
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_pl...
This record as markdown: /tools/com-tttkmbb-calcgrid/add-lt-working-days.md
What add_lt_working_days does on Calcgrid
AI agents use add_lt_working_days to create or update resources in Calcgrid, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Calcgrid environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
start_date | string | Yes | Gregorian start date in 2026-2026. |
working_days | integer | Yes | Signed offset; start date excluded for non-zero offsets. |
work_schedule | string | Yes | Required mon_fri_planning or mon_sat_planning. Choose the intended baseline explicitly; no universal or personal roster inferred. |
Parameters from the server's own tool schema.
Why add_lt_working_days is rated Medium
An AI agent can call add_lt_working_days faster than any human can review: one bad instruction and it creates or modifies resources in Calcgrid by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs add_lt_working_days safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Calcgrid, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For add_lt_working_days, this is the rule to start with:
add_lt_working_days stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Calcgrid, apply this rule, and every add_lt_working_days call is checked against it from then on.
Questions about add_lt_working_days
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. It is categorised as a Write tool in the Calcgrid MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
add_lt_working_days accepts 3 parameters: start_date, working_days, work_schedule. Required: start_date, working_days, work_schedule. The full parameter table on this page comes from the server's own tool schema.
Register the Calcgrid MCP server in PolicyLayer and add a rule for add_lt_working_days: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Calcgrid. Nothing to install.
add_lt_working_days is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the add_lt_working_days rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for add_lt_working_days. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
add_lt_working_days is provided by the Calcgrid MCP server (https://tttkmbb.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Calcgrid, and thousands of servers like it.
This server
Across the catalogue