count_lt_working_days
Use this when you need an auditable Lithuania working-day count. 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_planni...
This record as markdown: /tools/com-tttkmbb-calcgrid/count-lt-working-days.md
What count_lt_working_days does on Calcgrid
AI agents call count_lt_working_days to retrieve information from Calcgrid without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
end_date | string | Yes | Last date in 2026-2026. |
start_date | string | Yes | First date in 2026-2026. |
work_schedule | string | Yes | Required mon_fri_planning or mon_sat_planning. Choose the intended baseline explicitly; no universal or personal roster inferred. |
include_end_date | boolean | — | Whether end_date participates. |
include_start_date | boolean | — | Whether start_date participates. |
Parameters from the server's own tool schema.
Why count_lt_working_days is rated Low
Even though count_lt_working_days only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs count_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 count_lt_working_days, this is the rule to start with:
count_lt_working_days is read-only, so it stays allowed. 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 count_lt_working_days call is checked against it from then on.
Questions about count_lt_working_days
Use this when you need an auditable Lithuania working-day count. 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: Counts working/rest 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: Count Lithuania working days around Restoration of the State is a statutory holiday. | Count Lithuania working days around August 14 shortening is not full-day rest. | Count Lithuania working days around Good Friday is not an Article 123 rest day. | Count Lithuania working days around Easter eve depends on selected workweek. Inputs: start_date (date); end_date (date); include_start_date (boolean, optional); include_end_date (boolean, optional); work_schedule (enum). Complete JSON argument examples: {"start_date":"2026-01-01","end_date":"2026-12-31","work_schedule":"mon_fri_planning"} | {"start_date":"2026-01-01","end_date":"2026-12-31","work_schedule":"mon_sat_planning"} Outputs: working_days, non_working_days, public_holidays_counted, 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, shortened_work_dates_counted, shortened_work_date_count. 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-working-days-between with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/lithuania-public-working-days-between.md. It is categorised as a Read tool in the Calcgrid MCP Server, which means it retrieves data without modifying state.
count_lt_working_days accepts 5 parameters: end_date, start_date, work_schedule, include_end_date, include_start_date. Required: end_date, start_date, 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 count_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.
count_lt_working_days is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the count_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 count_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.
count_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