count_bg_working_days
Use this when you need an auditable Bulgaria 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 bulgaria 2026 nationwide statutory holidays, observed non-attendance days and January 2 on...
This record as markdown: /tools/com-tttkmbb-calcgrid/count-bg-working-days.md
What count_bg_working_days does on Calcgrid
AI agents call count_bg_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 explicit Monday-Friday planning baseline, not a universal legal roster. |
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_bg_working_days is rated Low
Even though count_bg_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_bg_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_bg_working_days, this is the rule to start with:
count_bg_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_bg_working_days call is checked against it from then on.
Questions about count_bg_working_days
Use this when you need an auditable Bulgaria 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 bulgaria 2026 nationwide statutory holidays, observed non-attendance days and January 2 one-off rest over an explicitly selected Monday-Friday planning baseline. November 1 is education-only and does not add general rest. No personal, shift, school, employer, bank/exchange, optional religious-leave, payroll or legal-deadline schedule is computed. Future years and additional local/sector closures are unsupported. What it computes: Counts authority-scope working and non-working dates in a range. Requires explicit mon_fri_planning; education-only holidays do not create general rest. Example user requests: Count Bulgaria working days around One-off euro transition rest, not statutory holiday. | Count Bulgaria working days around May 24 Sunday replacement. | Count Bulgaria working days around No nationwide school-holiday substitute. 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-04-09","end_date":"2026-04-14","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_holiday, is_observed_non_attendance_day, is_one_off_non_attendance_day, is_education_only_holiday, observed_for_dates, payroll_scope. Formula: planning_workday = weekday AND no nationwide statutory/observed/one-off rest event Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/bulgaria-public-working-days-between with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/bulgaria-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_bg_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_bg_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_bg_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_bg_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_bg_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_bg_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