check_global_working_day
Use this when you need a worldwide weekday/weekend check and have a CLDR alpha-2 territory code, but do not need public-holiday exclusions. 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 publi...
This record as markdown: /tools/com-tttkmbb-calcgrid/check-global-working-day.md
What check_global_working_day does on Calcgrid
AI agents call check_global_working_day 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 |
|---|---|---|---|
date | string | Yes | Gregorian date from 1900-01-01 through 2100-12-31. |
territory | string | Yes | CLDR territory code in alpha-2 form. The complete accepted-code enum is exposed here; it includes ISO-style territory codes plus CLDR regional and legacy codes |
Parameters from the server's own tool schema.
Why check_global_working_day is rated Low
Even though check_global_working_day 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 check_global_working_day 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 check_global_working_day, this is the rule to start with:
check_global_working_day 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 check_global_working_day call is checked against it from then on.
Questions about check_global_working_day
Use this when you need a worldwide weekday/weekend check and have a CLDR alpha-2 territory code, but do not need public-holiday exclusions. 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 public holidays, substitute holidays, employer closures, bank settlement, stock exchange, school, religious or emergency closure rules; use a jurisdiction-specific evidence package instead. What it computes: Checks a Gregorian date for any supported CLDR alpha-2 territory code using the pinned Unicode CLDR weekend convention, with explicit holiday exclusions and provenance. Example user requests: Is 2026-10-05 a working day in Australia under the territory weekend rule? | Check whether Friday 2026-06-12 is a weekday in Saudi Arabia. | 判断 2026-10-01 在印度按周末规则是否为工作日。 Inputs: date (date); territory (enum). Complete JSON argument examples: {"date":"2026-10-05","territory":"AU"} Outputs: date, territory, territory_display_name, weekday, is_working_day, weekend_days, calendar_scope, holiday_policy, calendar_profile, calendar_selection_catalog_url, dataset_version, source_url. Formula: is_working_day = weekday(date) not in CLDR(territory).weekendStart..weekendEnd Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/global-working-day with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/global-working-day.md. It is categorised as a Read tool in the Calcgrid MCP Server, which means it retrieves data without modifying state.
check_global_working_day accepts 2 parameters: date, territory. Required: date, territory. 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 check_global_working_day: 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.
check_global_working_day 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 check_global_working_day 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 check_global_working_day. 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.
check_global_working_day 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