add_ro_working_days
Use this when you need a deterministic Romania 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 romania 2026 statutory holiday layer only, with required calendar_basis and work_schedu...
This record as markdown: /tools/com-tttkmbb-calcgrid/add-ro-working-days.md
What add_ro_working_days does on Calcgrid
AI agents use add_ro_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 explicit Monday-Friday planning baseline; not an individual or universal legal roster. |
calendar_basis | string | Yes | Required date basis: romanian_orthodox or roman_catholic. Do not infer a person's religion or union calendars. |
Parameters from the server's own tool schema.
Why add_ro_working_days is rated Medium
An AI agent can call add_ro_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_ro_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_ro_working_days, this is the rule to start with:
add_ro_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_ro_working_days call is checked against it from then on.
Questions about add_ro_working_days
Use this when you need a deterministic Romania 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 romania 2026 statutory holiday layer only, with required calendar_basis and work_schedule=mon_fri_planning. The basis selects dates, not a person's identity or religion. No union of Christian calendars, non-Christian additional holidays, public-sector bridge/recovery days, individual rosters, shift exceptions, bank/exchange/school opening, payroll or legal deadlines are computed. Other bases and future years are unsupported. What it computes: Adds or subtracts Romania authority-scope working days in exact coverage. Explicit calendar_basis and mon_fri_planning required; no union of calendars or personal roster inference. Example user requests: Add or subtract Romania working days around January 24 remains a statutory holiday even on Saturday. | Add or subtract Romania working days around Selected-calendar Good Friday. Inputs: start_date (date); working_days (integer); calendar_basis (enum); work_schedule (enum). Complete JSON argument examples: {"start_date":"2026-01-01","working_days":0,"calendar_basis":"romanian_orthodox","work_schedule":"mon_fri_planning"} | {"start_date":"2026-01-01","working_days":0,"calendar_basis":"roman_catholic","work_schedule":"mon_fri_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, calendar_basis, work_schedule, is_statutory_holiday, payroll_scope, personal_roster_scope, additional_religious_holidays_scope. Formula: planning_workday = weekday AND no statutory holiday in the explicitly selected calendar_basis Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/romania-public-add-working-days with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/romania-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_ro_working_days accepts 4 parameters: start_date, working_days, work_schedule, calendar_basis. Required: start_date, working_days, 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 add_ro_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_ro_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_ro_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_ro_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_ro_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