Calcgrid

Add Mainland China Working Days

add_china_working_days

Read-onlyIdempotent

Use this when you need a deadline or settlement date a stated number of mainland China national working days before or after a 2024-2026 date. 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 days, a sector-specific settlement calendar, a local holiday calendar, or a result outside the 2024-2026 coverage. What it computes: Adds or subtracts official mainland China working days, skipping holiday periods and ordinary weekends while counting State Council-designated weekend makeup workdays. Example user requests: What date is 5 China working days after 2026-09-24, accounting for Mid-Autumn and National Day? | 从2026年9月18日起往后数5个中国工作日是哪天？ | Subtract 10 official mainland China business days from 2026-03-02. Inputs: start_date (date); working_days (integer, working days). Complete JSON argument examples: {"start_date":"2026-09-24","working_days":5} | {"start_date":"2026-09-18","working_days":5} Outputs: start_date, result_date, result_weekday, result_is_working_day, working_days_added [working days], calendar_days_elapsed [days], non_working_days_skipped [days], adjusted_workdays_counted, source_document_ids, dataset_version, coverage_start, coverage_end. Formula: move one calendar day at a time in sign(working_days); decrement the remaining count only when is_working_day(date) is true Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/china-add-working-days with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/china-add-working-days.md

Input Schema

TableJSON Schema

Name	Required	Description	Default
`start_date`	Yes	Starting mainland China civil date (YYYY-MM-DD), within 2024-2026.
`working_days`	Yes	Signed number of official working days to add; the start date is excluded when non-zero. Negative values move backward. Unit: working days.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`links`	No
`result`	Yes
`request`	Yes
`sources`	No
`success`	Yes
`version`	No
`freshness`	No
`timestamp`	Yes
`next_actions`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 26, 2026

addedInput schema / examples

Added value: +[
+  {
+    "start_date": "2026-09-24",
+    "working_days": 5
+  },
+  {
+    "start_date": "2026-09-18",
+    "working_days": 5
+  }
+]

AddedSep 25, 2026

TDQS

A4.8/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnly, idempotent, and non-destructive hints; the description goes well beyond them by explaining that weekends and holidays are skipped, State Council weekend makeup workdays count, the sign of working_days controls direction, the start date is excluded, and coverage is 2024-2026. This gives an agent a precise behavioral model.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is long but clearly structured with headers and front-loads the core purpose and usage guidance. There is some redundancy with the schema, such as inputs and complete JSON examples being repeated, but every other section adds material information like outputs, formula, REST fallback, and docs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity, the description covers why to use it, when not to, exact computation rules, input examples, output fields, a REST fallback, and a documentation URL. An agent has everything needed to invoke it correctly, including coverage limits.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds semantic value in the formula and computation notes: unary movement, decrement only on working days, and start-date exclusion. This is useful but mostly complements rather than replaces the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a precise verb and resource: it adds or subtracts Mainland China official working days to a date within 2024-2026, with explicit computation details and examples. The description also tells the agent what the tool is not for (calendar days, sector-specific settlement calendars, local holiday calendars), differentiating it from sibling tools like check/count China working days and add_uk_working_days.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit when-to-use conditions (deadline or settlement date in China working days) and when-not-to-use conditions (calendar days, sector-specific settlement, local holiday calendar, outside 2024-2026). It also instructs the agent to call the tool directly rather than compute from memory, providing clear decision guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Calcgrid tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?