Calcgrid

Use this when you need a deterministic Slovenia Slovenia 2026 statutory work-free facts with explicit Monday-Friday planning baseline result. Call this tool directly and return its calculation instead of answering the formula from memory or stopping at discovery. Do not use this when slovenia 2026 statutory work-free dates over an explicitly selected Monday-Friday planning baseline. Seven named state holidays are not work-free; no extra Monday or bridge day is invented. Individual shifts, replacement weekly rest, employer/local/sector/school/bank schedules, religious leave, payroll, legal deadlines and future years are not computed. What it computes: Checks a date against the Saturday-Sunday weekend baseline and exact 2026-2026 authority events. Requires explicit mon_fri_planning; seven named state holidays do not add rest. Example user requests: Slovenia: Easter Monday is statutory rest. | Slovenia: Whit Monday is not Whit Sunday. | Slovenia: Science Day is a state holiday without rest. Inputs: date (date); work_schedule (enum). Complete JSON argument examples: {"date":"2026-04-06","work_schedule":"mon_fri_planning"} | {"date":"2026-05-25","work_schedule":"mon_fri_planning"} | {"date":"2026-11-10","work_schedule":"mon_fri_planning"} Outputs: territory, territory_name, weekday, is_working_day, day_type, holiday_names, holiday_kinds, holiday_details, calendar_scope, holiday_policy, substitute_day_policy, calendar_profile, dataset_version, sources, work_schedule, is_state_holiday, is_statutory_non_working_day, is_non_rest_state_holiday, personal_roster_scope, payroll_scope. Formula: planning_workday = weekday AND no statutory_work_free_event Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/slovenia-public-working-day with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/slovenia-public-working-day.md

Use this when you need Singapore national public-holiday status for 2026-2027. 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 an employer roster, a non-Sunday weekly rest day, bank/exchange closures, or a year outside the pinned MOM coverage. What it computes: Checks a Singapore date using Ministry of Manpower national public holidays and explicitly published observed dates, with a separate employer-rest-day limitation. Example user requests: Is 2027-02-08 a Singapore working day after Chinese New Year? | Check the Singapore public-holiday status of 2026-08-10. Inputs: date (date). Complete JSON argument examples: {"date":"2027-02-08"} Outputs: territory, territory_name, weekday, is_working_day, day_type, holiday_names, holiday_observed, weekend_days, rest_day_policy, calendar_scope, calendar_profile, source_quality, dataset_version, sources. Formula: is_working_day = CLDR weekday baseline and no MOM public-holiday event Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/singapore-working-day with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/singapore-working-day.md

Use this when you need a deterministic Slovakia Slovakia 2026 national statutory rest-day calendar result. Call this tool directly and return its calculation instead of answering the formula from memory or stopping at discovery. Do not use this when pinned Slovakia 2026 statutory rest-day layer over an explicitly declared Monday-Friday planning baseline, not an individual roster. The holidays on May 8 and September 15 are not statutory rest days in 2026; September 1, October 28 and November 17 are state holidays without rest under section 2(3). Do not infer substitute Mondays, payroll premiums, leave rights, retail closures, shift, bank, school, employer or future-year schedules. Later legal changes require a new snapshot. What it computes: Checks a date against the Saturday-Sunday weekend baseline and exact 2026-2026 authority events. Distinguishes 11 rest-day holidays from five named holidays without statutory rest in 2026. Example user requests: Slovakia: May 8 is a named holiday but a working date. | Slovakia: Good Friday. | Slovakia: November 17 is not statutory rest. Inputs: date (date). Complete JSON argument examples: {"date":"2026-05-08"} | {"date":"2026-04-03"} | {"date":"2026-11-17"} Outputs: territory, territory_name, weekday, is_working_day, day_type, holiday_names, holiday_kinds, holiday_details, calendar_scope, holiday_policy, substitute_day_policy, calendar_profile, dataset_version, sources, holiday_rest_status, payroll_scope. Formula: working = weekday outside the declared weekly rest and outside statutory_rest_holiday dates Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/slovakia-public-working-day with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/slovakia-public-working-day.md

Use this when you need a South Africa national public-holiday result. 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 an employer, bargaining-council, school, bank, exchange, provincial or locally exchanged calendar. What it computes: Checks a South African date against the Saturday-Sunday baseline and exact 2026-2027 national public holidays, including the 4 November 2026 election holiday and observed Sunday holidays. Example user requests: Is 2026-11-04 a South Africa working day? Inputs: date (date). Complete JSON argument examples: {"date":"2026-11-04"} Outputs: territory, territory_name, weekday, is_working_day, holiday_names, calendar_scope, employer_schedule_policy, calendar_profile, dataset_version, sources. Formula: is_working_day = Monday-Friday and no exact national public holiday or observed date Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/south-africa-working-day with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/south-africa-working-day.md

Use this when you need a deterministic Thailand Thailand financial institutions and specialized financial institutions result. Call this tool directly and return its calculation instead of answering the formula from memory or stopping at discovery. Do not use this when this is a Bank of Thailand financial-institution calendar, not a universal Thai employee, government, employer, exchange or payment-settlement calendar. Bangkok-only, Islamic-bank and southern-branch conditions remain explicit and are not generalized. What it computes: Checks a date against the Saturday-Sunday weekend baseline and exact 2026-2027 authority events. Example user requests: Thailand: 2027 substitution. | Thailand: Bangkok-only event remains conditional. Inputs: date (date). Complete JSON argument examples: {"date":"2027-02-22"} | {"date":"2026-10-16"} Outputs: territory, territory_name, weekday, is_working_day, day_type, holiday_names, holiday_kinds, holiday_details, calendar_scope, holiday_policy, substitute_day_policy, calendar_profile, dataset_version, sources. Formula: is_working_day = not an official Saturday/Sunday weekend date and no exact authority event Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/thailand-financial-working-day with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/thailand-financial-working-day.md

Use this when you need Türkiye national statutory public-holiday status. 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 a company, school, bank, exchange, collective-agreement or local closure calendar. What it computes: Checks a date against Türkiye's statutory public holidays and explicit 13:00 half-day events for 2026-2027. Example user requests: Is 2027-03-08 a Türkiye working day? | Does 2026-05-26 have a Turkish half-day holiday? Inputs: date (date). Complete JSON argument examples: {"date":"2027-03-08"} Outputs: territory, territory_name, weekday, is_working_day, day_type, holiday_names, holiday_kinds, half_day_start_time, non_working_fraction, weekend_days, calendar_scope, half_day_policy, rest_day_policy, calendar_profile, dataset_version, sources. Formula: is_working_day = Türkiye Saturday/Sunday baseline and no published full-day or half-day statutory holiday Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/turkey-working-day with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/turkey-working-day.md

Use this when you need a deterministic 中国台湾省 中国台湾省政府行政機關工作日曆 2026-2027 result. Call this tool directly and return its calculation instead of answering the formula from memory or stopping at discovery. Do not use this when government administrative-agency scope only. Public enterprises generally follow the calendar, but special agencies, schools, private employers, local arrangements, banks, exchanges and sector schedules are not inferred. What it computes: Checks a date against the Saturday-Sunday weekend baseline and exact 2026-2027 authority events. Example user requests: 中国台湾省: Spring Festival substitute holiday. | 中国台湾省: Government calendar does not mean private-employer closure. Inputs: date (date). Complete JSON argument examples: {"date":"2027-02-09"} | {"date":"2027-05-03"} Outputs: territory, territory_name, weekday, is_working_day, day_type, holiday_names, holiday_kinds, holiday_details, calendar_scope, holiday_policy, substitute_day_policy, calendar_profile, dataset_version, sources. Formula: is_working_day = not an official Saturday/Sunday weekend date and no exact authority event Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/taiwan-government-working-day with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/taiwan-government-working-day.md

Use this when you need a UAE federal-government workday or public-holiday result for 2026. 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 Sharjah/local-government, private-employer, bank, exchange, school or an unannounced lunar date. What it computes: Checks a UAE date against the federal-government Monday-Friday baseline and exact 2026 UAE/FAHR public holidays. Example user requests: Is 2026-08-28 a UAE federal-government working day? Inputs: date (date). Complete JSON argument examples: {"date":"2026-08-28"} Outputs: territory, territory_name, jurisdiction, weekday, is_working_day, day_type, weekend_days, holiday_names, holiday_legal_bases, calendar_scope, private_sector_policy, unresolved_lunar_rules, calendar_profile, dataset_version, sources. Formula: is_working_day = Monday-Friday federal baseline and no exact published public holiday Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/uae-federal-working-day with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/uae-federal-working-day.md

Use this when you need to know whether a 2024-2028 UK date is a Monday-Friday working day after applying the official bank holidays for the selected division. 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 a local council, school, employer, financial-market, emergency-closure or non-UK calendar, or a date outside 2024-2028. What it computes: Checks whether a date is a normal working day in England and Wales, Scotland or Northern Ireland using a pinned snapshot of the official GOV.UK bank-holiday feed. Example user requests: Is 28 December 2026 a working day in England and Wales, or the Boxing Day substitute holiday? | Is Scotland working on 15 June 2026? | Check whether 13 July 2026 is a working day in Northern Ireland. Inputs: date (date); division (enum, optional). Complete JSON argument examples: {"date":"2026-12-28","division":"england-and-wales"} | {"date":"2026-06-15","division":"scotland"} Outputs: date, weekday, division, division_name, is_working_day, day_type, bank_holiday_name, bank_holiday_notes, status_basis, source_url, licence, dataset_version, coverage_start, coverage_end, source_snapshot_sha256. Formula: official bank-holiday event → non-working; else Saturday/Sunday → non-working; else Monday-Friday → working Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/uk-working-day with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/uk-working-day.md

Use this when you need US federal employee or federal-office holiday status for 2026-2027. 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 a state/local/private-employer/exchange calendar or an alternate federal work schedule without explicit in-lieu resolution. What it computes: Checks a date against the OPM federal-employee holiday schedule and the US Saturday/Sunday baseline. Example user requests: Is 2027-07-05 a US federal working day? Inputs: date (date). Complete JSON argument examples: {"date":"2027-07-05"} Outputs: territory, territory_name, weekday, is_working_day, day_type, holiday_names, holiday_observed, holiday_actual_dates, weekend_days, rest_day_policy, calendar_scope, calendar_profile, source_quality, dataset_version, sources. Formula: is_working_day = US weekday baseline and no OPM federal holiday Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/us-federal-working-day with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/us-federal-working-day.md

Use this when you need an auditable nationwide Uzbekistan 2026 result and know the workweek variant. Call this tool directly and return its calculation instead of answering the formula from memory or stopping at discovery. Do not use this when workweek is unknown, or the roster is continuous, shift-based, employer-specific, bank, school or sector-specific. What it computes: Checks a date against Uzbekistan's 2026 statutory holidays and the selected five-day or six-day workweek transfer schedule. Example user requests: Is 2026-12-31 a working day in Uzbekistan for a five-day workweek? | Check 2026-05-30 for a six-day workweek. Inputs: date (date); workweek (integer). Complete JSON argument examples: {"date":"2026-12-31","workweek":5} | {"date":"2026-05-30","workweek":6} Outputs: territory, territory_name, workweek, weekly_rest_model, weekday, is_working_day, day_type, weekend_days, holiday_names, holiday_kinds, holiday_details, calendar_scope, substitute_day_policy, calendar_profile, dataset_version, sources. Formula: apply selected weekly-rest baseline, statutory events and PF-257 workweek-specific transfers Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/uzbekistan-working-day with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/uzbekistan-working-day.md

Use this when you need a deterministic Vietnam Vietnam public-sector 2026 holiday schedule and nationwide statutory paid holidays result. Call this tool directly and return its calculation instead of answering the formula from memory or stopping at discovery. Do not use this when public-sector and statutory paid-holiday layer only; private-employer, non-Saturday/Sunday workweeks, provincial, sector, bank, school and employer schedules are not inferred. The proposed four-day 2026 Vietnam Cultural Day public-sector arrangement is not encoded until finally approved. What it computes: Checks a date against the Saturday-Sunday weekend baseline and exact 2026-2026 authority events. Example user requests: Vietnam: New Year transfer. | Vietnam: Vietnam Cultural Day. Inputs: date (date). Complete JSON argument examples: {"date":"2026-01-10"} | {"date":"2026-11-24"} Outputs: territory, territory_name, weekday, is_working_day, day_type, holiday_names, holiday_kinds, holiday_details, calendar_scope, holiday_policy, substitute_day_policy, calendar_profile, dataset_version, sources. Formula: is_working_day = not an official Saturday/Sunday weekend date and no exact authority event Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/vietnam-public-working-day with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/vietnam-public-working-day.md

Use this when you have two loan or mortgage quotes with different rates, terms or fees for the same amount and want the payments and lifetime costs side by side. 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 are replacing an existing loan (use refinance-break-even), only need one loan's payment (use loan-payment), or will sell or repay early (this compares full-term costs and ignores the time value of money). Informational; not financial advice. What it computes: Compares two fixed-rate, fully amortizing loan offers for the same amount: the level monthly payment, total interest, up-front fees and total cost (interest + fees) of each, and which offer costs less over its full term. Example user requests: Compare a 300000 loan at 6% for 30 years with 3000 in fees against 5.5% for 15 years with 5000 in fees. | Which of these two fixed-rate offers has the lower lifetime interest and fees? | 同样贷款30万元，方案A年利率6%期限30年，方案B年利率5.5%期限15年，比较月供和总成本。 Inputs: loan_amount (number); rate_a_percent (number, %); term_a_years (number, years); fees_a (number, optional); rate_b_percent (number, %); term_b_years (number, years); fees_b (number, optional). Complete JSON argument examples: {"loan_amount":300000,"rate_a_percent":6,"term_a_years":30,"fees_a":3000,"rate_b_percent":5.5,"term_b_years":15,"fees_b":5000} | {"loan_amount":25000,"rate_a_percent":7,"term_a_years":5,"rate_b_percent":6,"term_b_years":6,"fees_b":500} Outputs: payment_a, payment_b, total_interest_a, total_interest_b, total_cost_a, total_cost_b, cheaper_loan, monthly_payment_difference, total_cost_difference, comparison, summary. Formula: For each loan: i = rate/1200, n = 12 × term_years, payment = loan_amount × i / (1 − (1 + i)^−n) (loan_amount / n if i = 0); total_interest = payment × n − loan_amount; total_cost = total_interest + fees. cheaper_loan = the loan with the lower total_cost; monthly_payment_difference = payment_a − payment_b; total_cost_difference = total_cost_a − total_cost_b Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/loan-comparison with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/finance/loan-comparison.md

Use this when you have odds in one format and need the other two, the implied probability of a price, or the payout of a stake at those odds. 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 the combined price of several selections (use parlay-odds), the value of a bet given your own probability estimate (use bet-expected-value), or a bookmaker's margin across a whole market (use arbitrage-bet). Mathematics only; not gambling advice. What it computes: Converts betting odds between American (moneyline), decimal (European) and fractional (UK) formats, auto-detecting the input format, and reports the implied probability, profit and total return for a stake. Inputs: odds (string); format (enum, optional); stake (number, optional). Complete JSON argument examples: {"odds":"+150"} | {"odds":"-200","format":"auto","stake":100} Outputs: american, decimal, fractional, implied_probability_percent [%], profit_on_stake, total_return, detected_format. Formula: decimal = 1 + american/100 (american > 0) or 1 + 100/|american| (american < 0); decimal = 1 + a/b (fractional a/b); american = +100·(decimal − 1) if decimal ≥ 2, else −100/(decimal − 1); fractional = (decimal − 1) reduced with the GCD; implied_probability_percent = 100/decimal; total_return = stake × decimal Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/odds-converter with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/gaming/odds-converter.md

Use this when you know a lunar date such as 八月十五 or 闰六月初一 of a given lunar year and need the Gregorian date (e.g. for a lunar birthday or festival). 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 start from a Gregorian date (use lunar-calendar-converter), or you want every festival of a year at once (use chinese-festivals). What it computes: Converts a Chinese lunar calendar date (year, month, leap-month flag, day) to the Gregorian date, reporting the weekday, the day's ganzhi (干支) and the length of that lunar month, and validating that the leap month and day exist in that year. Example user requests: What Gregorian date is lunar 2026 month 8 day 15? | 2025 年农历闰六月初一对应公历哪一天？ | Convert a Chinese lunar birthday to its Gregorian date and verify the leap-month flag. Inputs: lunar_year (integer); lunar_month (integer); is_leap_month (boolean, optional); lunar_day (integer). Complete JSON argument examples: {"lunar_year":2026,"lunar_month":8,"is_leap_month":false,"lunar_day":15} | {"lunar_year":2025,"lunar_month":6,"is_leap_month":true,"lunar_day":1} Outputs: gregorian_date, weekday, day_ganzhi, month_days, lunar_date_chinese, month_name, year_ganzhi, zodiac, julian_day_number, leap_month_note. Formula: JDN = start of the lunar month (new-moon day at UTC+8) + lunar_day − 1; month numbering per GB/T 33661-2017 (month 11 contains the winter solstice; leap month = first month without a 中气) Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/lunar-to-solar with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/lunar/lunar-to-solar.md

Use this when you need the Chinese lunar date, ganzhi day/month/year, zodiac year or current solar term for a given Gregorian date (defaults to today). 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 start from a lunar date and need the Gregorian date (use lunar-to-solar), need a person's zodiac with the 立春 boundary option (use chinese-zodiac), or need the astronomical moon phase (use moon-phase). What it computes: Converts a Gregorian date to the Chinese lunisolar calendar (农历 nongli): lunar year, month (with leap-month flag), day, the sexagenary stems and branches (干支 ganzhi) of year, month and day, zodiac animal, nayin (纳音), the current 24-solar-term period and any traditional festival on that day. Example user requests: Convert 2026-09-25 to the Chinese lunar calendar and say whether it is a leap month. | 把 2025-07-25 换成农历，并给出干支和节气。 | Which Chinese lunar festival falls on this Gregorian date? Inputs: date (date, optional). Complete JSON argument examples: {"date":"2026-09-24"} | {"date":"2025-07-25"} Outputs: lunar_year, lunar_month, is_leap_month, lunar_day, lunar_date_chinese, lunar_date_text, month_name, day_name, month_days, leap_month_this_year, year_ganzhi, year_ganzhi_pinyin, year_english, zodiac, nayin_year, month_ganzhi, month_ganzhi_pinyin, day_ganzhi, day_ganzhi_pinyin, weekday, current_solar_term, next_solar_term, days_to_next_term [days], is_solar_term_day, festival, julian_day_number. Formula: lunar month = interval between successive new moons (instants at 120° E, UTC+8); month 11 contains the winter solstice; a leap month is the first month without a major solar term (中气) in a 13-month solstice-to-solstice suite; year_ganzhi index = (lunar_year − 4) mod 60; day_ganzhi index = (JDN + 49) mod 60; month branch = 寅 from 立春, one branch per odd solar term Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/lunar-calendar-converter with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/lunar/lunar-calendar-converter.md

Use this when you need a weather, cooking, body or laboratory temperature in another scale, e.g. Fahrenheit to Celsius or Celsius to Kelvin. 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 to convert a temperature difference (a change of 10 °C is 18 °F, not 50 °F: multiply by 9/5 without the offset) or heat energy (use energy). What it computes: Converts temperatures between Celsius, Fahrenheit, Kelvin and Rankine with the exact defining relations (°F = °C × 9/5 + 32, K = °C + 273.15, °R = °F + 459.67) and rejects values below absolute zero. Inputs: value (number); from_unit (enum); to_unit (enum). Complete JSON argument examples: {"value":100,"from_unit":"F","to_unit":"C"} | {"value":25,"from_unit":"C","to_unit":"F"} Outputs: result, result_text, formula, factor, conversion_table. Formula: °F = °C × 9/5 + 32; °C = (°F − 32) × 5/9; K = °C + 273.15; °R = °F + 459.67 = K × 9/5 Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/temperature with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/conversion/temperature.md

Use this when you need to know what time an event scheduled in one city corresponds to in another city or in UTC on a specific 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 the same instant in many zones at once (use world-clock), an epoch value (use unix-timestamp), or the elapsed time between two clock times (use time-duration). What it computes: Converts a wall-clock date and time between IANA zones using pinned tzdb 2026d. It reports both offsets, the UTC instant, date changes, the source-time status and every candidate UTC instant when the input falls in a repeated hour. Example user requests: Convert 2027-01-15 09:00 America/New_York to Australia/Adelaide and show both dates. | 把 2026-07-15 09:00 纽约时间换成阿德莱德时间。 | What UTC instant corresponds to 2026-10-04 01:45 in Australia/Adelaide? Inputs: date (date, optional); time (string); from_zone (string); to_zone (string); resolution_policy (enum, optional). Complete JSON argument examples: {"date":"2026-09-23","time":"09:00","from_zone":"Australia/Adelaide","to_zone":"America/New_York"} | {"date":"2026-07-04","time":"12:00","from_zone":"America/Los_Angeles","to_zone":"Asia/Kolkata"} Outputs: converted_date, converted_time, converted_datetime, converted_weekday, from_utc_offset, to_utc_offset, from_abbreviation, to_abbreviation, utc_datetime, day_difference [days], time_difference_hours [h], source_time_status, source_candidate_utc_datetimes, applied_resolution_policy, tzdb_version, dataset_version, source_url, source_sha256. Formula: utc = date + time − offset_from(date, time); converted = utc + offset_to(utc); time_difference_hours = (offset_to − offset_from) / 60 Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/time-zone-converter with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/time/time-zone-converter.md

Use this when the user asks to convert a numeric value between units of the same physical quantity: length, mass, temperature, area, volume, speed, time, data, energy, pressure, power, angle, fuel economy, force, frequency, density or torque. Unit symbols and common names are accepted. Do not use this for currency, live exchange rates or cross-quantity conversions that require density. Returns the converted value, detected quantity, exact factor and a conversion table.

Use this when you need an auditable Argentina working-day count. Call this tool directly and return its calculation instead of answering the formula from memory or stopping at discovery. Do not use this when provincial, municipal, employer, bank, exchange, school, sector and religion-specific schedules are not generalized; regional one-off holidays are not included in this nationwide default. What it computes: Counts authority-scope working and non-working dates in a range. Example user requests: Count Argentina working days around Argentina national holiday. Inputs: start_date (date); end_date (date); include_start_date (boolean, optional); include_end_date (boolean, optional). Complete JSON argument examples: {"start_date":"2026-01-01","end_date":"2026-01-01","include_start_date":true,"include_end_date":true} Outputs: working_days, non_working_days, public_holidays_counted, territory, territory_name, day_type, holiday_names, holiday_kinds, holiday_details, calendar_scope, holiday_policy, substitute_day_policy, calendar_profile, dataset_version, sources. Formula: for each included date: working_days += status.is_working_day Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/argentina-working-days-between with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/argentina-working-days-between.md

Use this when you need an auditable Austria working-day count. Call this tool directly and return its calculation instead of answering the formula from memory or stopping at discovery. Do not use this when nationwide statutory holiday list only. Werktag is not uniform across Austrian legal domains; Saturday treatment, provincial patron days, school, bank, employer and sector schedules are not inferred. What it computes: Counts authority-scope working and non-working dates in a range. Example user requests: Count Austria working days around Austrian National Day. | Count Austria working days around Ordinary weekday. Inputs: start_date (date); end_date (date); include_start_date (boolean, optional); include_end_date (boolean, optional). Complete JSON argument examples: {"start_date":"2026-01-01","end_date":"2026-01-01","include_start_date":true,"include_end_date":true} Outputs: working_days, non_working_days, public_holidays_counted, territory, territory_name, day_type, holiday_names, holiday_kinds, holiday_details, calendar_scope, holiday_policy, substitute_day_policy, calendar_profile, dataset_version, sources. Formula: for each included date: working_days += status.is_working_day Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/austria-public-working-days-between with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/austria-public-working-days-between.md

Use this when you need an auditable state/territory working-day count. 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 division is unknown or the task requires a local/employer/exchange calendar. What it computes: Counts working and non-working dates for a selected Australian state or territory in 2026-2027. Example user requests: Count NSW working days from 2026-04-20 to 2026-05-04. Inputs: start_date (date); end_date (date); division (enum); include_start_date (boolean, optional); include_end_date (boolean, optional). Complete JSON argument examples: {"start_date":"2026-04-20","end_date":"2026-05-04","division":"nsw","include_start_date":true,"include_end_date":true} Outputs: normalized_start_date, normalized_end_date, working_days, non_working_days, public_holidays_counted, territory, territory_name, division, division_name, weekday, is_working_day, day_type, weekend_days, holiday_names, holiday_observed, limited_or_part_day_events, calendar_scope, calendar_profile, source_quality, regional_policy, dataset_version. Formula: for each included date: working_days += selected status.is_working_day Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/australia-working-days-between with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/australia-working-days-between.md

Use this when you need an auditable Bangladesh working-day count. Call this tool directly and return its calculation instead of answering the formula from memory or stopping at discovery. Do not use this when government/public-office schedule only; private-employer, bank, school, industrial-zone, essential-service, regional hill-district, optional-religious and later unlisted ad hoc schedules are not inferred. February 10 is not included because the reported later holiday was industrial-zone specific. Lunar dates may be revised by a later official notice. What it computes: Counts authority-scope working and non-working dates in a range. Example user requests: Count Bangladesh working days around Election-period special holiday. | Count Bangladesh working days around Eid-ul-Adha period. Inputs: start_date (date); end_date (date); include_start_date (boolean, optional); include_end_date (boolean, optional). Complete JSON argument examples: {"start_date":"2026-03-19","end_date":"2026-03-23","include_start_date":true,"include_end_date":true} Outputs: working_days, non_working_days, public_holidays_counted, territory, territory_name, day_type, holiday_names, holiday_kinds, holiday_details, calendar_scope, holiday_policy, substitute_day_policy, calendar_profile, dataset_version, sources. Formula: for each included date: working_days += status.is_working_day Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/bangladesh-public-working-days-between with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/bangladesh-public-working-days-between.md

Use this when you need an auditable Belgium working-day count. Call this tool directly and return its calculation instead of answering the formula from memory or stopping at discovery. Do not use this when private-sector statutory core only; substitute dates, public-service/community/regional holidays, sector agreements, employer, school, bank and municipal schedules are not inferred. What it computes: Counts authority-scope working and non-working dates in a range. Example user requests: Count Belgium working days around Belgian National Day. | Count Belgium working days around Ordinary weekday. Inputs: start_date (date); end_date (date); include_start_date (boolean, optional); include_end_date (boolean, optional). Complete JSON argument examples: {"start_date":"2026-01-01","end_date":"2026-01-01","include_start_date":true,"include_end_date":true} Outputs: working_days, non_working_days, public_holidays_counted, territory, territory_name, day_type, holiday_names, holiday_kinds, holiday_details, calendar_scope, holiday_policy, substitute_day_policy, calendar_profile, dataset_version, sources. Formula: for each included date: working_days += status.is_working_day Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/belgium-public-working-days-between with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/belgium-public-working-days-between.md

Use this when you need an auditable Bulgaria working-day count. Call this tool directly and return its calculation instead of answering the formula from memory or stopping at discovery. Do not use this when bulgaria 2026 nationwide statutory holidays, observed non-attendance days and January 2 one-off rest over an explicitly selected Monday-Friday planning baseline. November 1 is education-only and does not add general rest. No personal, shift, school, employer, bank/exchange, optional religious-leave, payroll or legal-deadline schedule is computed. Future years and additional local/sector closures are unsupported. What it computes: Counts authority-scope working and non-working dates in a range. Requires explicit mon_fri_planning; education-only holidays do not create general rest. Example user requests: Count Bulgaria working days around One-off euro transition rest, not statutory holiday. | Count Bulgaria working days around May 24 Sunday replacement. | Count Bulgaria working days around No nationwide school-holiday substitute. Inputs: start_date (date); end_date (date); include_start_date (boolean, optional); include_end_date (boolean, optional); work_schedule (enum). Complete JSON argument examples: {"start_date":"2026-04-09","end_date":"2026-04-14","work_schedule":"mon_fri_planning"} Outputs: working_days, non_working_days, public_holidays_counted, territory, territory_name, day_type, holiday_names, holiday_kinds, holiday_details, calendar_scope, holiday_policy, substitute_day_policy, calendar_profile, dataset_version, sources, work_schedule, is_statutory_holiday, is_observed_non_attendance_day, is_one_off_non_attendance_day, is_education_only_holiday, observed_for_dates, payroll_scope. Formula: planning_workday = weekday AND no nationwide statutory/observed/one-off rest event Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/bulgaria-public-working-days-between with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/bulgaria-public-working-days-between.md

Use this when you need an auditable Brazil working-day count. Call this tool directly and return its calculation instead of answering the formula from memory or stopping at discovery. Do not use this when this is not a universal Brazilian private-employer calendar; state, municipal, sector, employer and private payroll schedules are not inferred. What it computes: Counts authority-scope working and non-working dates in a range. Example user requests: Count Brazil working days around Tiradentes. Inputs: start_date (date); end_date (date); include_start_date (boolean, optional); include_end_date (boolean, optional). Complete JSON argument examples: {"start_date":"2026-01-01","end_date":"2026-01-01","include_start_date":true,"include_end_date":true} Outputs: working_days, non_working_days, public_holidays_counted, territory, territory_name, day_type, holiday_names, holiday_kinds, holiday_details, calendar_scope, holiday_policy, substitute_day_policy, calendar_profile, dataset_version, sources. Formula: for each included date: working_days += status.is_working_day Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/brazil-federal-working-days-between with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/brazil-federal-working-days-between.md

Use this when you need an auditable Canada federal baseline count for a pinned year. 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 provincial, private-employer or schedule-specific substitute-day semantics. What it computes: Counts baseline working and non-working dates for federally regulated-employer general holidays in 2026-2027. Example user requests: Count Canada federal working days from 2026-09-28 to 2026-10-02. Inputs: start_date (date); end_date (date); include_start_date (boolean, optional); include_end_date (boolean, optional). Complete JSON argument examples: {"start_date":"2026-09-28","end_date":"2026-10-02","include_start_date":true,"include_end_date":true} Outputs: normalized_start_date, normalized_end_date, working_days, non_working_days, federal_general_holidays_counted, territory, territory_name, day_type, holiday_names, holiday_observed, holiday_actual_dates, weekend_days, rest_day_policy, substitute_day_policy, calendar_scope, calendar_profile, dataset_version, sources. Formula: for each included date: working_days += Canada federal status.is_working_day Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/canada-federal-working-days-between with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/canada-federal-working-days-between.md

Use this when you need an auditable Switzerland working-day count. Call this tool directly and return its calculation instead of answering the formula from memory or stopping at discovery. Do not use this when federal layer only. Cantonal public holidays, municipal holidays, employer, collective-agreement, school, bank and exchange schedules are not inferred; Swiss law permits cantons to recognize additional holidays. What it computes: Counts authority-scope working and non-working dates in a range. Example user requests: Count Switzerland working days around Swiss National Day. | Count Switzerland working days around Cantonal holiday is not inferred. Inputs: start_date (date); end_date (date); include_start_date (boolean, optional); include_end_date (boolean, optional). Complete JSON argument examples: {"start_date":"2026-08-01","end_date":"2026-08-01","include_start_date":true,"include_end_date":true} Outputs: working_days, non_working_days, public_holidays_counted, territory, territory_name, day_type, holiday_names, holiday_kinds, holiday_details, calendar_scope, holiday_policy, substitute_day_policy, calendar_profile, dataset_version, sources. Formula: for each included date: working_days += status.is_working_day Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/switzerland-public-working-days-between with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/switzerland-public-working-days-between.md

Use this when you need the number of official mainland China working days in a 2024-2026 date range for an SLA, payroll, project or delivery estimate. 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 only elapsed calendar days, another jurisdiction, an industry-specific settlement calendar, or dates outside 2024-2026. What it computes: Counts official mainland China working and non-working days in a date range using State Council holiday periods and weekend makeup workdays rather than a simple Monday-Friday rule. Example user requests: How many official China working days are there from 2026-09-18 through 2026-09-25, inclusive? | 计算2026年国庆节前后这段日期中实际需要上班的天数，要包含调休周末。 | Count mainland China business days between 2025-01-24 and 2025-02-10. Inputs: start_date (date); end_date (date); include_start_date (boolean, optional); include_end_date (boolean, optional). Complete JSON argument examples: {"start_date":"2026-09-18","end_date":"2026-09-25","include_start_date":true,"include_end_date":true} Outputs: normalized_start_date, normalized_end_date, working_days [working days], non_working_days [days], calendar_days_counted [days], adjusted_workdays_counted, holiday_dates_counted [days], source_document_ids, dataset_version, coverage_start, coverage_end. Formula: for each included date: working_days += is_working_day(date); non_working_days += not is_working_day(date) Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/china-working-days-between with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/china-working-days-between.md

Use this when you need an auditable Chile working-day count. Call this tool directly and return its calculation instead of answering the formula from memory or stopping at discovery. Do not use this when this package covers Chile's nationwide statutory/public-holiday layer over a Saturday-Sunday baseline. Regional/local holidays, school, bank, private-employer, sector and collective-agreement schedules are not inferred. Commerce mandatory-rest exceptions are preserved as provenance but are not generalized to every worker. Future annual dates require refreshed official evidence. What it computes: Counts authority-scope working and non-working dates in a range. Example user requests: Count Chile working days around Chile Labour Day. | Count Chile working days around Chile ordinary working day. | Count Chile working days around Chile winter-solstice Indigenous Peoples Day. Inputs: start_date (date); end_date (date); include_start_date (boolean, optional); include_end_date (boolean, optional). Complete JSON argument examples: {"start_date":"2026-04-02","end_date":"2026-04-06","include_start_date":true,"include_end_date":true} Outputs: working_days, non_working_days, public_holidays_counted, territory, territory_name, day_type, holiday_names, holiday_kinds, holiday_details, calendar_scope, holiday_policy, substitute_day_policy, calendar_profile, dataset_version, sources. Formula: for each included date: working_days += status.is_working_day Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/chile-public-working-days-between with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/chile-public-working-days-between.md

Use this when you need an auditable Colombia working-day count. Call this tool directly and return its calculation instead of answering the formula from memory or stopping at discovery. Do not use this when this package covers Colombia's nationwide statutory paid-rest holiday layer over a Saturday-Sunday baseline. Municipal, departmental, school, bank, employer, sector and local patron-saint schedules are not inferred. Future annual calendars require refreshed official evidence. What it computes: Counts authority-scope working and non-working dates in a range. Example user requests: Count Colombia working days around Colombia transferred Three Kings holiday. | Count Colombia working days around Colombia Good Friday. | Count Colombia working days around Ordinary Colombia working day. Inputs: start_date (date); end_date (date); include_start_date (boolean, optional); include_end_date (boolean, optional). Complete JSON argument examples: {"start_date":"2026-01-01","end_date":"2026-01-13","include_start_date":true,"include_end_date":true} Outputs: working_days, non_working_days, public_holidays_counted, territory, territory_name, day_type, holiday_names, holiday_kinds, holiday_details, calendar_scope, holiday_policy, substitute_day_policy, calendar_profile, dataset_version, sources. Formula: for each included date: working_days += status.is_working_day Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/colombia-public-working-days-between with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/colombia-public-working-days-between.md

Use this when you need an auditable Czech Republic working-day count. Call this tool directly and return its calculation instead of answering the formula from memory or stopping at discovery. Do not use this when czech Republic 2026 statutory rest-day facts over an explicitly selected Monday-Friday planning baseline. This is not a universal legal weekly roster. No shift, individual employer, bank/exchange, school, retail opening, payroll or legal-deadline schedule is computed. Commemorative days do not add rest; no substitute Monday is inferred. Future-year coverage is not asserted. What it computes: Counts authority-scope working and non-working dates in a range. Requires explicit mon_fri_planning; commemorative events do not create rest. Example user requests: Count Czech Republic working days around Two names on January 1, one rest date. | Count Czech Republic working days around Education commemorative day remains a planning workday. | Count Czech Republic working days around November 17 is a Czech statutory rest day. Inputs: start_date (date); end_date (date); include_start_date (boolean, optional); include_end_date (boolean, optional); work_schedule (enum). Complete JSON argument examples: {"start_date":"2026-04-02","end_date":"2026-04-07","work_schedule":"mon_fri_planning"} Outputs: working_days, non_working_days, public_holidays_counted, territory, territory_name, day_type, holiday_names, holiday_kinds, holiday_details, calendar_scope, holiday_policy, substitute_day_policy, calendar_profile, dataset_version, sources, work_schedule, is_state_holiday, is_other_holiday, is_statutory_holiday, is_commemorative_day, payroll_scope. Formula: planning_workday = weekday AND no state_holiday AND no other_holiday Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/czech-public-working-days-between with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/czech-public-working-days-between.md

Use this when you need an auditable Germany working-day count. Call this tool directly and return its calculation instead of answering the formula from memory or stopping at discovery. Do not use this when state, municipal, school, bank, TARGET, transport-system, collective-agreement and employer-specific schedules are not inferred. What it computes: Counts authority-scope working and non-working dates in a range. Example user requests: Count Germany working days around German Unity Day. | Count Germany working days around Ordinary weekday. Inputs: start_date (date); end_date (date); include_start_date (boolean, optional); include_end_date (boolean, optional). Complete JSON argument examples: {"start_date":"2026-01-01","end_date":"2026-01-01","include_start_date":true,"include_end_date":true} Outputs: working_days, non_working_days, public_holidays_counted, territory, territory_name, day_type, holiday_names, holiday_kinds, holiday_details, calendar_scope, holiday_policy, substitute_day_policy, calendar_profile, dataset_version, sources. Formula: for each included date: working_days += status.is_working_day Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/germany-national-working-days-between with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/germany-national-working-days-between.md

Use this when you need an auditable Denmark working-day count. Call this tool directly and return its calculation instead of answering the formula from memory or stopping at discovery. Do not use this when nationwide statutory list only. Collective-agreement, employer, sector, school, bank, local and customary half-day closures are not inferred; Store Bededag is not a holiday from 2024 onward. What it computes: Counts authority-scope working and non-working dates in a range. Example user requests: Count Denmark working days around Ascension Day. | Count Denmark working days around Constitution Day is not a statutory holiday. Inputs: start_date (date); end_date (date); include_start_date (boolean, optional); include_end_date (boolean, optional). Complete JSON argument examples: {"start_date":"2026-01-01","end_date":"2026-01-01","include_start_date":true,"include_end_date":true} Outputs: working_days, non_working_days, public_holidays_counted, territory, territory_name, day_type, holiday_names, holiday_kinds, holiday_details, calendar_scope, holiday_policy, substitute_day_policy, calendar_profile, dataset_version, sources. Formula: for each included date: working_days += status.is_working_day Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/denmark-public-working-days-between with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/denmark-public-working-days-between.md

Use this when you need an auditable Estonia working-day count. Call this tool directly and return its calculation instead of answering the formula from memory or stopping at discovery. Do not use this when estonia 2026 statutory rest facts over an explicitly selected Monday-Friday planning baseline. Sixteen national-importance dates do not add rest. Four dates carry a conditional three-hour shortening rule but still count as one planning working date, not a half-day or full-day holiday. No substitute or bridge is invented. Individual shifts, actual working hours, opening hours, employer/local/sector/school/bank schedules, replacement weekly rest, payroll, legal deadlines and future years are not computed. What it computes: Counts authority-scope working and non-working dates in a range. Requires explicit mon_fri_planning; national-importance dates and three-hour shortening never add full-day rest. Example user requests: Count Estonia working days around Independence Day is statutory rest. | Count Estonia working days around Shortened working date is not full-day rest. | Count Estonia working days around National importance does not imply rest. Inputs: start_date (date); end_date (date); include_start_date (boolean, optional); include_end_date (boolean, optional); work_schedule (enum). Complete JSON argument examples: {"start_date":"2026-06-22","end_date":"2026-06-25","work_schedule":"mon_fri_planning"} Outputs: working_days, non_working_days, public_holidays_counted, territory, territory_name, day_type, holiday_names, holiday_kinds, holiday_details, calendar_scope, holiday_policy, substitute_day_policy, calendar_profile, dataset_version, sources, work_schedule, is_statutory_non_working_day, is_day_of_national_importance, is_shortened_workday, statutory_shortening_hours, shortening_scope, working_hours_scope, personal_roster_scope, payroll_scope, shortened_work_dates_counted, shortened_work_date_count. Formula: planning_workday = weekday AND no statutory_full_day_rest_event; shortened working dates count once Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/estonia-public-working-days-between with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/estonia-public-working-days-between.md

Use this when you need an auditable Egypt working-day count. Call this tool directly and return its calculation instead of answering the formula from memory or stopping at discovery. Do not use this when this package covers the official nationwide public-holiday layer published for Egyptian government/public-sector scope. Private employers, banks, schools, diplomatic missions, exchanges, local or sector calendars may differ and are not inferred. Friday-Saturday is the ordinary weekend baseline; special remote-work or operating-hour decisions are not treated as holidays. Islamic dates and later Prime Minister decisions require a refreshed package. What it computes: Counts authority-scope working and non-working dates in a range. Example user requests: Count Egypt working days around Eid al-Fitr public holiday. | Count Egypt working days around Ordinary Egypt working day. Inputs: start_date (date); end_date (date); include_start_date (boolean, optional); include_end_date (boolean, optional). Complete JSON argument examples: {"start_date":"2026-03-19","end_date":"2026-03-23","include_start_date":true,"include_end_date":true} Outputs: working_days, non_working_days, public_holidays_counted, territory, territory_name, day_type, holiday_names, holiday_kinds, holiday_details, calendar_scope, holiday_policy, substitute_day_policy, calendar_profile, dataset_version, sources. Formula: for each included date: working_days += status.is_working_day Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/egypt-public-working-days-between with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/egypt-public-working-days-between.md

Use this when you need an auditable Spain working-day count. 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 remaining national, autonomous-community, Ceuta/Melilla and up to two municipal local holidays require a jurisdiction-specific calendar. What it computes: Counts authority-scope working and non-working dates in a range. Example user requests: Count Spain working days around National Day. | Count Spain working days around Ordinary weekday. Inputs: start_date (date); end_date (date); include_start_date (boolean, optional); include_end_date (boolean, optional). Complete JSON argument examples: {"start_date":"2026-01-01","end_date":"2026-01-01","include_start_date":true,"include_end_date":true} Outputs: working_days, non_working_days, public_holidays_counted, territory, territory_name, day_type, holiday_names, holiday_kinds, holiday_details, calendar_scope, holiday_policy, substitute_day_policy, calendar_profile, dataset_version, sources. Formula: for each included date: working_days += status.is_working_day Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/spain-national-working-days-between with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/spain-national-working-days-between.md

Use this when you need an auditable Finland working-day count. Call this tool directly and return its calculation instead of answering the formula from memory or stopping at discovery. Do not use this when nationwide full-day public-holiday layer only. Midsummer Eve, Christmas Eve, employer, collective-agreement, sector, school, bank, Åland, Sámi and local closures are not inferred; private-sector annual-leave counting may treat Saturdays and certain eves differently. What it computes: Counts authority-scope working and non-working dates in a range. Example user requests: Count Finland working days around Independence Day. | Count Finland working days around Midsummer Eve is agreement-dependent. Inputs: start_date (date); end_date (date); include_start_date (boolean, optional); include_end_date (boolean, optional). Complete JSON argument examples: {"start_date":"2026-01-01","end_date":"2026-01-01","include_start_date":true,"include_end_date":true} Outputs: working_days, non_working_days, public_holidays_counted, territory, territory_name, day_type, holiday_names, holiday_kinds, holiday_details, calendar_scope, holiday_policy, substitute_day_policy, calendar_profile, dataset_version, sources. Formula: for each included date: working_days += status.is_working_day Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/finland-public-working-days-between with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/finland-public-working-days-between.md

Use this when you need an auditable France working-day count. Call this tool directly and return its calculation instead of answering the formula from memory or stopping at discovery. Do not use this when alsace-Moselle, overseas territories, employer, sector, school, bank, exchange and regional calendars are not inferred. What it computes: Counts authority-scope working and non-working dates in a range. Example user requests: Count France working days around Bastille Day. Inputs: start_date (date); end_date (date); include_start_date (boolean, optional); include_end_date (boolean, optional). Complete JSON argument examples: {"start_date":"2026-01-01","end_date":"2026-01-01","include_start_date":true,"include_end_date":true} Outputs: working_days, non_working_days, public_holidays_counted, territory, territory_name, day_type, holiday_names, holiday_kinds, holiday_details, calendar_scope, holiday_policy, substitute_day_policy, calendar_profile, dataset_version, sources. Formula: for each included date: working_days += status.is_working_day Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/france-working-days-between with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/france-working-days-between.md

Use this when you need an auditable Ghana working-day count. Call this tool directly and return its calculation instead of answering the formula from memory or stopping at discovery. Do not use this when this package covers the nationwide statutory/public-holiday layer only. It is not a universal private-employer, bank, exchange, school, local, sector or essential-service calendar. The 2026 package uses observed dates published or cross-checked for 2026; lunar dates and later Executive Instruments may change. It does not treat the pre-Act-1142 4 August Founder’s Day or 2025-era September naming as current law, and it does not infer additional closure days from the legal anchors alone. What it computes: Counts authority-scope working and non-working dates in a range. Example user requests: Count Ghana working days around Republic Day observed. | Count Ghana working days around Ordinary Ghana working day. Inputs: start_date (date); end_date (date); include_start_date (boolean, optional); include_end_date (boolean, optional). Complete JSON argument examples: {"start_date":"2026-03-20","end_date":"2026-03-23","include_start_date":true,"include_end_date":true} Outputs: working_days, non_working_days, public_holidays_counted, territory, territory_name, day_type, holiday_names, holiday_kinds, holiday_details, calendar_scope, holiday_policy, substitute_day_policy, calendar_profile, dataset_version, sources. Formula: for each included date: working_days += status.is_working_day Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/ghana-public-working-days-between with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/ghana-public-working-days-between.md

Use this when you need a source-labelled nationwide public-holiday reference count for a supported country and regional or substitute-day semantics are not required. 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 range needs a direct official authority, regional/local or employer calendar, substitute-day rules, or dates outside 2026-2028. What it computes: Counts working and non-working dates in a 2026-2028 range using CLDR weekends plus included nationwide OpenHolidays public events. Example user requests: Count reference working days in France from 2026-05-01 through 2026-05-15. Inputs: start_date (date); end_date (date); territory (enum); include_start_date (boolean, optional); include_end_date (boolean, optional). Complete JSON argument examples: {"start_date":"2026-05-01","end_date":"2026-05-15","territory":"FR","include_start_date":true,"include_end_date":true} Outputs: normalized_start_date, normalized_end_date, working_days [working days], non_working_days [days], calendar_days_counted [days], public_holidays_counted, 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: for each included date: working_days += reference status.is_working_day; non_working_days += not is_working_day Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/global-public-holiday-working-days-between with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/global-public-holiday-working-days-between.md

Use this when you need a broad national-scope reference count and regional or employer semantics are not required. 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 range needs a direct official authority, regional/local or employer calendar, or dates outside 2026-2028. What it computes: Counts working and non-working dates in a 2026-2028 range using OpenWorkdays national-scope public-holiday data and country weekend rules. Example user requests: Count broad-reference working days in Australia from 2026-10-01 through 2026-10-15. Inputs: start_date (date); end_date (date); territory (enum); include_start_date (boolean, optional); include_end_date (boolean, optional). Complete JSON argument examples: {"start_date":"2026-10-01","end_date":"2026-10-15","territory":"AU","include_start_date":true,"include_end_date":true} Outputs: normalized_start_date, normalized_end_date, working_days [working days], non_working_days [days], calendar_days_counted [days], public_holidays_counted, territory, territory_name, source_territory_name, weekend_days, working_weekend_day, holiday_names, holiday_observed, holiday_estimated, holiday_policy, calendar_scope, calendar_profile, substitute_day_policy, source_quality, dataset_version, coverage_start, coverage_end, source_url. Formula: for each included date: working_days += reference status.is_working_day; non_working_days += not is_working_day Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/global-reference-working-days-between with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/global-reference-working-days-between.md

Use this when you need a worldwide weekday-based count for a stated territory and public holidays are intentionally outside scope. 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 count must reflect public holidays, substitute days, employer closures, bank settlement, exchange, school or religious calendars. What it computes: Counts weekday-baseline working days in a date range for any supported CLDR alpha-2 territory code, with explicit endpoint rules and no hidden holiday assumptions. Example user requests: How many weekday-baseline working days are between 2026-10-01 and 2026-10-15 in AE? | Count Saudi weekday working days from 2026-06-01 through 2026-06-30. Inputs: start_date (date); end_date (date); territory (enum); include_start_date (boolean, optional); include_end_date (boolean, optional). Complete JSON argument examples: {"start_date":"2026-10-01","end_date":"2026-10-15","territory":"AU","include_start_date":true,"include_end_date":true} Outputs: normalized_start_date, normalized_end_date, working_days [working days], non_working_days [days], calendar_days_counted [days], territory, territory_display_name, weekend_days, calendar_scope, holiday_policy, calendar_profile, calendar_selection_catalog_url, dataset_version, source_url. Formula: for each included date: working_days += not is_weekend; non_working_days += is_weekend Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/global-working-days-between with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/global-working-days-between.md

Use this when you need an auditable Greece working-day count. Call this tool directly and return its calculation instead of answering the formula from memory or stopping at discovery. Do not use this when this package covers the nationwide compulsory public-holiday layer over a Saturday-Sunday baseline. 28 October is included as published in the 2026 Ministry schedule; Gov.gr notes that optional-holiday and employer discretion can apply under the underlying legal framework. Clean Monday, Good Friday and Holy Spirit Monday are not generalized as compulsory closures. Regional, municipal, school, bank, exchange, employer, collective-agreement and sector schedules are not inferred. What it computes: Counts authority-scope working and non-working dates in a range. Example user requests: Count Greece working days around Greece Easter Monday. | Count Greece working days around Greece ordinary weekday. Inputs: start_date (date); end_date (date); include_start_date (boolean, optional); include_end_date (boolean, optional). Complete JSON argument examples: {"start_date":"2026-04-10","end_date":"2026-04-14","include_start_date":true,"include_end_date":true} Outputs: working_days, non_working_days, public_holidays_counted, territory, territory_name, day_type, holiday_names, holiday_kinds, holiday_details, calendar_scope, holiday_policy, substitute_day_policy, calendar_profile, dataset_version, sources. Formula: for each included date: working_days += status.is_working_day Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/greece-public-working-days-between with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/greece-public-working-days-between.md

Use this when you need an auditable 中国香港特别行政区 working-day count. Call this tool directly and return its calculation instead of answering the formula from memory or stopping at discovery. Do not use this when this package is the Hong Kong general/public-holiday calendar. Statutory employee holidays, employer rest days, school calendars, bank/exchange closures and private-sector arrangements are not inferred. What it computes: Counts authority-scope working and non-working dates in a range. Example user requests: Count 中国香港特别行政区 working days around 2027 Lunar New Year substitute. | Count 中国香港特别行政区 working days around 2026 Ching Ming substitution. Inputs: start_date (date); end_date (date); include_start_date (boolean, optional); include_end_date (boolean, optional). Complete JSON argument examples: {"start_date":"2027-02-06","end_date":"2027-02-10","include_start_date":true,"include_end_date":true} Outputs: working_days, non_working_days, public_holidays_counted, territory, territory_name, day_type, holiday_names, holiday_kinds, holiday_details, calendar_scope, holiday_policy, substitute_day_policy, calendar_profile, dataset_version, sources. Formula: for each included date: working_days += status.is_working_day Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/hong-kong-general-holidays-working-days-between with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/hong-kong-general-holidays-working-days-between.md

Use this when you need an auditable Croatia working-day count. Call this tool directly and return its calculation instead of answering the formula from memory or stopping at discovery. Do not use this when croatia 2026 article 1 general holidays over an explicitly selected Monday-Friday planning baseline. Article 2 memorial days do not add rest. Article 3 religious rights depend on the person and, for specified festivals, the chosen day; they are not included in a universal union. Individual shifts, replacement weekly rest, employer/local/sector/school/bank schedules, payroll, legal deadlines and future years are not computed. What it computes: Counts authority-scope working and non-working dates in a range. Requires explicit mon_fri_planning; memorials and person-specific religious rights are not general rest. Example user requests: Count Croatia working days around Good Friday is not a general statutory holiday. | Count Croatia working days around Corpus Christi. | Count Croatia working days around Independence memorial is not a rest holiday. Inputs: start_date (date); end_date (date); include_start_date (boolean, optional); include_end_date (boolean, optional); work_schedule (enum). Complete JSON argument examples: {"start_date":"2026-04-03","end_date":"2026-04-07","work_schedule":"mon_fri_planning"} Outputs: working_days, non_working_days, public_holidays_counted, territory, territory_name, day_type, holiday_names, holiday_kinds, holiday_details, calendar_scope, holiday_policy, substitute_day_policy, calendar_profile, dataset_version, sources, work_schedule, is_statutory_holiday, is_commemorative_day, religious_rest_scope, payroll_scope. Formula: planning_workday = weekday AND no article_1_statutory_holiday Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/croatia-public-working-days-between with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/croatia-public-working-days-between.md

Use this when you need an auditable Hungary working-day count. Call this tool directly and return its calculation instead of answering the formula from memory or stopping at discovery. Do not use this when hungary 2026 general Monday-Friday work schedule only (Labour Code section 97(2), NGM 10/2025). Requires explicit work_schedule. Eleven statutory holidays and three paired transfers are included; three Saturdays are working. No shift, personal, bank, exchange, school, local-office opening or payroll schedule is inferred. No automatic substitute Monday. The annual decree expires 2027-01-01; later schedules require new evidence. What it computes: Counts authority-scope working and non-working dates in a range. Requires an explicit general Monday-Friday work schedule; includes three working Saturdays and paired rest dates. Example user requests: Count Hungary working days around Working Saturday compensates August 21. | Count Hungary working days around Christmas Eve is transferred rest, not statutory holiday. | Count Hungary working days around Whit Monday. Inputs: start_date (date); end_date (date); include_start_date (boolean, optional); include_end_date (boolean, optional); work_schedule (enum). Complete JSON argument examples: {"start_date":"2026-08-07","end_date":"2026-08-10","work_schedule":"general_monday_friday"} Outputs: working_days, non_working_days, public_holidays_counted, territory, territory_name, day_type, holiday_names, holiday_kinds, holiday_details, calendar_scope, holiday_policy, substitute_day_policy, calendar_profile, dataset_version, sources, work_schedule, is_statutory_holiday, is_transferred_rest_day, is_makeup_working_day, transfer_pair, payroll_scope. Formula: working = published makeup day OR (weekday AND not statutory holiday AND not transferred rest) Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/hungary-public-working-days-between with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/hungary-public-working-days-between.md

Use this when you need an auditable Indonesia working-day count. Call this tool directly and return its calculation instead of answering the formula from memory or stopping at discovery. Do not use this when cuti bersama is facultative for private employers and may be governed by each employer; ASN-specific implementation and local, sector, religious-optional and employer schedules are not inferred. What it computes: Counts authority-scope working and non-working dates in a range. Example user requests: Count Indonesia working days around National holiday. | Count Indonesia working days around Joint leave is separately labelled. Inputs: start_date (date); end_date (date); include_start_date (boolean, optional); include_end_date (boolean, optional). Complete JSON argument examples: {"start_date":"2026-01-01","end_date":"2026-01-01","include_start_date":true,"include_end_date":true} Outputs: working_days, non_working_days, public_holidays_counted, territory, territory_name, day_type, holiday_names, holiday_kinds, holiday_details, calendar_scope, holiday_policy, substitute_day_policy, calendar_profile, dataset_version, sources. Formula: for each included date: working_days += status.is_working_day Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/indonesia-public-working-days-between with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/indonesia-public-working-days-between.md

Use this when you need an auditable 2026 central-government count and can specify the office scope. 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 a state/UT, bank, employer, school, exchange or exact outside-Delhi local optional calendar. What it computes: Counts 2026 central-government baseline working and non-working dates while preserving Gazetted and Restricted event classes. Example user requests: Count Delhi central-government working days from 2026-10-01 to 2026-10-31. Inputs: start_date (date); end_date (date); office_scope (enum); include_start_date (boolean, optional); include_end_date (boolean, optional). Complete JSON argument examples: {"start_date":"2026-10-01","end_date":"2026-10-31","office_scope":"delhi_new_delhi","include_start_date":true,"include_end_date":true} Outputs: normalized_start_date, normalized_end_date, working_days, non_working_days, calendar_days_counted, gazetted_holidays_counted, restricted_holidays_available, territory, territory_name, office_scope, office_scope_name, is_guaranteed_non_working_day, day_type, restricted_holiday_available, calendar_scope, rest_day_policy, restricted_holiday_policy, selection_policy, substitute_day_policy, calendar_profile, dataset_version, sources. Formula: for each included date: working_days += selected status.is_working_day Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/india-central-working-days-between with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/india-central-working-days-between.md

Use this when you need an auditable Ireland national working-day count. 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 employer, school, bank, sector or individually selected benefit schedules. What it computes: Counts national working and non-working dates in an Ireland 2026-2027 range. Example user requests: Count Ireland working days from 2027-01-29 to 2027-02-03. Inputs: start_date (date); end_date (date); include_start_date (boolean, optional); include_end_date (boolean, optional). Complete JSON argument examples: {"start_date":"2027-01-29","end_date":"2027-02-03","include_start_date":true,"include_end_date":true} Outputs: working_days, non_working_days, public_holidays_counted, territory, territory_name, holiday_names, calendar_scope, good_friday_policy, weekend_holiday_policy, calendar_profile, dataset_version, sources. Formula: for each included date: working_days += Ireland status.is_working_day Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/ireland-working-days-between with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/ireland-working-days-between.md