count_lv_working_days

Use this when you need an auditable Latvia 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 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: Counts authority-scope working and non-working dates in a range. Explicit transfer basis and mon_fri_planning required. Separate statutory rest, non-rest observances, transferred work/rest and conditional shortening. Example user requests: Count Latvia working days around Mother's Day is statutory even on Sunday. | Count Latvia working days around January 2 depends on explicit transfer basis. | Count Latvia working days around June 27 depends on explicit transfer basis. Inputs: start_date (date); end_date (date); include_start_date (boolean, optional); include_end_date (boolean, optional); calendar_basis (enum); work_schedule (enum). Complete JSON argument examples: {"start_date":"2026-01-01","end_date":"2026-12-31","calendar_basis":"statutory_holidays_only","work_schedule":"mon_fri_planning"} | {"start_date":"2026-01-01","end_date":"2026-12-31","calendar_basis":"cabinet_order_330_transfers","work_schedule":"mon_fri_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, 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, shortened_work_dates_counted, shortened_work_date_count. 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-working-days-between with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/latvia-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_lv_working_days accepts 6 parameters: end_date, start_date, work_schedule, calendar_basis, include_end_date, include_start_date. Required: end_date, start_date, work_schedule, calendar_basis. 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_lv_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_lv_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_lv_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_lv_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_lv_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.