count_ee_working_days

Use this when you need an auditable Estonia 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 estonia 2026 statutory rest facts over an explicitly selected Monday-Friday planning baseline. Sixteen national-importance dates do not add rest. Four dates carry a conditional three-hour shortening rule but still count as one planning working date, not a half-day or full-day holiday. No substitute or bridge is invented. Individual shifts, actual working hours, opening hours, employer/local/sector/school/bank schedules, replacement weekly rest, payroll, legal deadlines and future years are not computed. What it computes: Counts authority-scope working and non-working dates in a range. Requires explicit mon_fri_planning; national-importance dates and three-hour shortening never add full-day rest. Example user requests: Count Estonia working days around Independence Day is statutory rest. | Count Estonia working days around Shortened working date is not full-day rest. | Count Estonia working days around National importance does not imply rest. 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-06-22","end_date":"2026-06-25","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, work_schedule, is_statutory_non_working_day, is_day_of_national_importance, 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 = weekday AND no statutory_full_day_rest_event; shortened working dates count once Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/estonia-public-working-days-between with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/estonia-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_ee_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_ee_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_ee_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_ee_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_ee_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_ee_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.