calculate_business_deadline
Use this when you need an SLA, support, procurement or order deadline measured in business hours under the published mainland China or UK calendar, and must express the result in another team's IANA time zone with reproducible holiday and DST evidence. Call this tool directly and return its calcu...
This record as markdown: /tools/com-tttkmbb-calcgrid/calculate-business-deadline.md
What calculate_business_deadline does on Calcgrid
AI agents use calculate_business_deadline 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 |
|---|---|---|---|
calendar | string | Yes | Versioned public working-day calendar that determines which local dates may consume business hours. |
business_hours | number | Yes | Positive duration consumed only inside eligible working-date windows. It is rounded to the nearest second. Unit: hours. |
start_time_zone | string | Yes | IANA zone used for the start time and every daily business window. |
business_day_end | string | Yes | Local closing/cutoff time on each eligible working date. Must be later than business_day_start on the same date. |
target_time_zone | string | Yes | IANA zone in which the same deadline should also be returned for the receiving team. |
include_start_day | boolean | Yes | True counts eligible time remaining on the start local date; false skips that entire local date and starts at the next working opening. |
resolution_policy | string | — | How to resolve an ambiguous or nonexistent start wall time. reject is safest; earlier/later select a repeated instant; shift_forward moves a gap time by the DST |
business_day_start | string | Yes | Local opening time on each eligible working date. Must be earlier than business_day_end; overnight windows are not supported. |
start_local_datetime | string | Yes | Start wall-clock date and time without an offset. start_time_zone supplies its IANA zone. |
Parameters from the server's own tool schema.
Why calculate_business_deadline is rated Medium
An AI agent can call calculate_business_deadline 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 calculate_business_deadline 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 calculate_business_deadline, this is the rule to start with:
calculate_business_deadline 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 calculate_business_deadline call is checked against it from then on.
Questions about calculate_business_deadline
Use this when you need an SLA, support, procurement or order deadline measured in business hours under the published mainland China or UK calendar, and must express the result in another team's IANA time zone with reproducible holiday and DST evidence. Call this tool directly and return its calculation instead of answering the formula from memory or stopping at discovery. Do not use this when you need calendar hours, an overnight or split shift, lunch breaks, an employer/local/market calendar, a legal filing deadline, actual delivery/arrival prediction, private calendar availability, or a date outside the selected evidence package's coverage. What it computes: Adds an explicit number of business hours inside a caller-supplied daily window, using either the official mainland China work calendar or a selected GOV.UK division, then returns the deadline in UTC, the calendar zone and a target IANA zone with a complete segment/skip audit trail. Example user requests: A Shanghai support ticket opened at 2026-09-24 15:00 has a 16-business-hour SLA, counted from that day during 09:00-17:00 China official working time. When is it due in London? | Starting 24 December 2026 at 15:00 London time, add 8 England-and-Wales business hours between 09:00 and 17:00 and show the deadline in Shanghai. | 按中国官方工作日，从 2026-09-24 15:00（上海）起计算 16 个营业小时，每天 09:00-17:00，起始日计入；给出伦敦时间和跳过日期。 Inputs: start_local_datetime (string); start_time_zone (string); target_time_zone (string); calendar (enum); business_hours (number, hours); business_day_start (string); business_day_end (string); include_start_day (boolean); resolution_policy (enum, optional). Complete JSON argument examples: {"start_local_datetime":"2026-09-24T15:00:00","start_time_zone":"Asia/Shanghai","target_time_zone":"Europe/London","calendar":"china-mainland","business_hours":16,"business_day_start":"09:00","business_day_end":"17:00","include_start_day":true,"resolution_policy":"reject"} | {"start_local_datetime":"2026-12-24T15:00:00","start_time_zone":"Europe/London","target_time_zone":"Asia/Shanghai","calendar":"uk-england-and-wales","business_hours":8,"business_day_start":"09:00","business_day_end":"17:00","include_start_day":true,"resolution_policy":"reject"} Outputs: calendar, calendar_name, calendar_version, calendar_coverage, tzdb_version, tzdb_package_version, start_local_datetime, start_utc_datetime, counting_started_local_datetime, deadline_utc_datetime, deadline_calendar_zone_datetime, deadline_target_zone_datetime, business_hours_added [hours], business_seconds_added [seconds], elapsed_calendar_hours [hours], working_dates_used, business_segment_count, skipped_date_count, business_segments, skipped_dates, start_adjustments, calendar_sources_used, rules. Formula: deadline = consume business_hours only inside [business_day_start, business_day_end) on dates where the selected versioned calendar reports is_working_day=true; convert each local boundary with pinned IANA tzdb Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/business-hours-deadline with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/business/business-hours-deadline.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.
calculate_business_deadline accepts 9 parameters: calendar, business_hours, start_time_zone, business_day_end, target_time_zone, include_start_day, resolution_policy, business_day_start, start_local_datetime. Required: calendar, business_hours, start_time_zone, business_day_end, target_time_zone, include_start_day, business_day_start, start_local_datetime. 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 calculate_business_deadline: 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.
calculate_business_deadline 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 calculate_business_deadline 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 calculate_business_deadline. 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.
calculate_business_deadline 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