Calcgrid

Add Global Public-Holiday Reference Working Days

add_global_public_holiday_working_days

Read-onlyIdempotent

Use this when you need a 2026-2028 date offset and accept the OpenHolidays nationwide-only, no-inferred-substitute-day reference semantics. Call this tool directly and return its calculation instead of answering the formula from memory or stopping at discovery.

Do not use this when the task requires a direct official authority, regional/local or employer calendar, substitute-day rules, or dates outside the published coverage. What it computes: Adds or subtracts working days using the pinned OpenHolidays nationwide public-holiday reference and CLDR weekend rule for a supported country. Example user requests: Add five reference working days to 2026-10-23 in Austria. Inputs: start_date (date); territory (enum); working_days (integer, working days). Complete JSON argument examples: {"start_date":"2026-10-23","territory":"AT","working_days":5} Outputs: start_date, result_date, working_days_added [working days], calendar_days_elapsed [days], non_working_weekend_days_skipped [days], public_holidays_skipped, territory, territory_name, weekend_days, holiday_names, holiday_policy, calendar_scope, calendar_profile, substitute_day_policy, source_quality, dataset_version, coverage_start, coverage_end, source_commit. Formula: move one Gregorian day at a time; decrement remaining only when the reference status is_working_day=true Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/global-public-holiday-add-working-days with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/global-public-holiday-add-working-days.md

Input Schema

TableJSON Schema

Name	Required	Description
`territory`	Yes	ISO-style alpha-2 country code supported by the pinned OpenHolidays public-holiday reference snapshot.
`start_date`	Yes	Gregorian start date in 2026-2028.
`working_days`	Yes	Signed offset; the start date is excluded for non-zero offsets. Unit: working days.

Output Schema

TableJSON Schema

Name	Required	Description
`links`	No
`result`	Yes
`request`	Yes
`sources`	No
`success`	Yes
`version`	No
`freshness`	No
`timestamp`	Yes
`next_actions`	No
`service_version`	Yes	Deployed Calcgrid implementation version used for the result.

Schema Changelog

Changes observed during successful MCP inspections.

AddedSep 28, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent/openWorld=false, and the description adds substantive behavior beyond them: the exact reference semantics, the CLDR weekend rule, coverage window, substitute-day policy, the day-by-day counting formula, the output units, and a pinned REST fallback with a warning not to guess other paths.

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?

Front-loaded with usage and exclusions in labelled sections that are easy to scan, but it is long and carries some redundancy (re-listing all ~17 output fields, duplicating the JSON example already in the schema, and restating the REST URL).

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 a 3-parameter, high-coverage schema with an output schema and multiple near-identical siblings, the description covers semantics, scope, sourcing, formula, fallback endpoint, and docs link. Nothing an agent needs to select or invoke it correctly is missing.

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

Parameters3/5

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

Schema description coverage is 100%, so all three parameters are already documented (including the alpha-2 pattern, date format, and signed-offset unit). The description's Inputs line largely restates the schema and adds no new format or boundary meaning, so the baseline 3 applies.

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 specific verb (adds/subtracts working days) plus the pinned reference source, scope (nationwide-only OpenHolidays, 2026-2028) and a concrete example request. It is clearly distinguishable from siblings like count_global_public_holiday_working_days or check_global_public_holiday_working_day.

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?

Explicit when-to-use (need a 2026-2028 offset and accept nationwide-only, no-inferred-substitute-day semantics; call directly instead of answering from memory) and an explicit do-not-use clause (official authority, regional/local or employer calendars, substitute-day rules, out-of-coverage dates). This is textbook routing 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?