Calcgrid

Use this when you need an auditable Italy 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 regional, municipal, local patron-saint, school, bank, sector, 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 Italy working days around Republic Day. | Count Italy working days around Easter Monday. 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/italy-public-working-days-between with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/italy-public-working-days-between.md

Use this when you need an auditable Japan statutory national-holiday 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 a company, school, bank, exchange or prefectural closure calendar. What it computes: Counts Japan statutory-baseline working and non-working dates for a pinned year range. Example user requests: Count Japan working days from 2027-03-01 to 2027-03-31. Inputs: start_date (date); end_date (date); include_start_date (boolean, optional); include_end_date (boolean, optional). Complete JSON argument examples: {"start_date":"2027-03-01","end_date":"2027-03-31","include_start_date":true,"include_end_date":true} Outputs: normalized_start_date, normalized_end_date, working_days, non_working_days, national_holidays_counted, territory, territory_name, day_type, holiday_names, holiday_kinds, holiday_legal_bases, weekend_days, calendar_scope, rest_day_policy, calendar_profile, dataset_version, sources. Formula: for each included date: working_days += Japan national status.is_working_day Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/japan-national-working-days-between with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/japan-national-working-days-between.md

Use this when you need an auditable Kenya 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 public-holiday layer only. It is not a universal private-employer, bank, school, county, sector, diplomatic or shift-work calendar. The Saturday-Sunday baseline is a calculation convention for ordinary weekday work, not a claim that every employer uses the same roster. Idd-ul-Fitr and Idd-ul-Adha are pinned to the 2026 Gazette declarations; future lunar dates and later special notices require a refreshed package. The Act's Sunday substitution rule is preserved and no Saturday-to-Monday substitution is inferred. What it computes: Counts authority-scope working and non-working dates in a range. Example user requests: Count Kenya working days around Idd-ul-Fitr public holiday. | Count Kenya working days around Ordinary Kenya 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-04-03","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/kenya-public-working-days-between with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/kenya-public-working-days-between.md

Use this when you need an auditable South Korea 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 package covers the 2026 statutory/public-office schedule only; private-employer, school, bank, exchange, local-government and 2027 schedules are not inferred. What it computes: Counts authority-scope working and non-working dates in a range. Example user requests: Count South Korea working days around New Labor Day public holiday. | Count South Korea working days around Published substitute 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/south-korea-public-working-days-between with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/south-korea-public-working-days-between.md

Use this when you need an auditable Kazakhstan 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 published 2026 five-day schedule over a Saturday-Sunday baseline. Six-day, shift, continuous-operation, employer, bank, school, local and sector calendars are not inferred. Qurban Ait is represented by the published 2026 first-day date. Adilet's current text records Constitution Day on 15 March with an amendment effective 2026-07-01, while the published 2026 government calendar does not add a March 15/16 closure; this package follows the published 2026 calendar and future-year packages must refresh the legal transition. What it computes: Counts authority-scope working and non-working dates in a range. Example user requests: Count Kazakhstan working days around Nauryz transfer day. | Count Kazakhstan 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-03-21","end_date":"2026-03-25","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/kazakhstan-public-working-days-between with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/kazakhstan-public-working-days-between.md

Use this when you need an auditable Sri Lanka 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 a combined official holiday-class calendar, not a universal private-employer closure rule. Public, bank and mercantile classifications remain in each event kind; the March 18, March 25 and April 1 fuel-conservation entries apply to government offices only and the schedule was cancelled effective April 8. Essential services, schools, private employers, sector agreements, local arrangements and later unlisted notices are not inferred. The additional day after the National Vesak Festival is not invented beyond the published May 2 calendar entry. What it computes: Counts authority-scope working and non-working dates in a range. Example user requests: Count Sri Lanka working days around Poya holiday. | Count Sri Lanka working days around Temporary government-office Wednesday. 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-13","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/sri-lanka-public-working-days-between with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/sri-lanka-public-working-days-between.md

Use this when you need an auditable Lithuania 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 lithuania 2026 Labour Code holiday facts with explicit mon_fri_planning or mon_sat_planning. Sixteen full-day statutory holidays; pre-holiday one-hour rules do not create additional rest. No weekend substitution or bridge is inferred. Required work_schedule selects a planning calendar, not a universal personal roster. Actual hours, pay, shifts, local/employer/sector/school/bank schedules, religious personal leave, legal deadlines and future years are not computed. What it computes: Counts working/rest dates in the explicitly selected Lithuania 2026 five-day or six-day planning workweek. Sixteen statutory holidays; conditional one-hour eve markers never add full-day rest. Example user requests: Count Lithuania working days around Restoration of the State is a statutory holiday. | Count Lithuania working days around August 14 shortening is not full-day rest. | Count Lithuania working days around Good Friday is not an Article 123 rest day. | Count Lithuania working days around Easter eve depends on selected workweek. 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-01-01","end_date":"2026-12-31","work_schedule":"mon_fri_planning"} | {"start_date":"2026-01-01","end_date":"2026-12-31","work_schedule":"mon_sat_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_preholiday_rule_date, 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 = day in selected workweek AND no statutory_holiday_rest; shortened work dates count once Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/lithuania-public-working-days-between with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/lithuania-public-working-days-between.md

Use this when you need an auditable Luxembourg 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 luxembourg 2026-2028 statutory holiday dates over an explicitly selected Monday-Friday planning baseline, BEFORE individual annual or compensatory leave. A holiday on a normally non-worked day may produce compensatory leave depending on the employee's schedule, hours and applicable rules; no compensation date or next-Monday closure is assigned here. Bank-only Good Friday/Christmas Eve afternoon, customary or collectively agreed holidays, school/local/employer/shift schedules, hours, payroll, personal entitlements and legal deadlines are not computed. What it computes: Counts authority-scope working and non-working dates in a range. Requires explicit mon_fri_planning; personal compensatory leave and bank-only closures are not computed. Example user requests: Count Luxembourg working days around Europe Day is statutory rest. | Count Luxembourg working days around No uniform Monday compensation date. | Count Luxembourg working days around Bank-only Good Friday is not general statutory 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-05-08","end_date":"2026-05-11","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, holiday_on_baseline_weekend, compensatory_leave_scope, compensatory_date_policy, personal_roster_scope, payroll_scope, weekend_holiday_dates_counted, weekend_holiday_date_count. Formula: planning_workday = weekday AND no statutory_holiday_rest; individual leave is not deducted Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/luxembourg-public-working-days-between with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/luxembourg-public-working-days-between.md

Use this when you need an auditable Latvia 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 latvia 2026 only. Explicit calendar_basis and work_schedule=mon_fri_planning are required. The transfer basis applies Cabinet Order 330 only when the organization is covered or has adopted it; no private employer adoption is inferred. Section 2 observances do not add rest. Shortening is conditional, not full-day rest. Six-day/shift/personal rosters, other religious calendars, bank/exchange/school opening, payroll, actual hours and legal deadlines are not computed. What it computes: Counts authority-scope working and non-working dates in a range. Explicit transfer basis and mon_fri_planning required. Separate statutory rest, non-rest observances, transferred work/rest and conditional shortening. Example user requests: Count Latvia working days around Mother's Day is statutory even on Sunday. | Count Latvia working days around January 2 depends on explicit transfer basis. | Count Latvia working days around June 27 depends on explicit transfer basis. Inputs: start_date (date); end_date (date); include_start_date (boolean, optional); include_end_date (boolean, optional); calendar_basis (enum); work_schedule (enum). Complete JSON argument examples: {"start_date":"2026-01-01","end_date":"2026-12-31","calendar_basis":"statutory_holidays_only","work_schedule":"mon_fri_planning"} | {"start_date":"2026-01-01","end_date":"2026-12-31","calendar_basis":"cabinet_order_330_transfers","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, calendar_basis, work_schedule, is_statutory_holiday, is_non_rest_observance, is_transferred_rest_day, is_transferred_working_day, is_shortened_workday, statutory_shortening_hours, shortening_scope, payroll_scope, personal_roster_scope, working_hours_scope, additional_religious_holidays_scope, shortened_work_dates_counted, shortened_work_date_count. Formula: planning_workday = explicit transferred working date OR (weekday AND no statutory/selected transferred rest); shortened dates count once Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/latvia-public-working-days-between with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/latvia-public-working-days-between.md

Use this when you need an auditable Malta 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 malta 2026 named statutory holidays and Sunday public-holiday status over an explicitly selected Monday-Friday planning baseline BEFORE individual annual or compensatory leave. Additional vacation entitlement for a named holiday on a weekly rest day depends on the person's employment and roster; no next-Monday or later leave date is assigned. Bank-only, school, local, employer and shift calendars, hours, payroll, personal entitlements and legal deadlines are not computed. Future years require a separately verified package. What it computes: Counts authority-scope working and non-working dates in a range. Required mon_fri_planning; named holidays and Sunday statutory status remain distinct. Personal leave and bank-only dates are not computed. Example user requests: Count Malta working days around Good Friday is scheduled public rest. | Count Malta working days around Ordinary Sunday is public holiday, not a named holiday. | Count Malta working days around No invented Monday compensation. 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-05","end_date":"2026-06-08","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_public_holiday, is_named_statutory_holiday, is_national_holiday, is_other_scheduled_public_holiday, is_sunday_public_holiday, holiday_on_baseline_weekend, sunday_legal_basis, compensatory_leave_scope, personal_roster_scope, payroll_scope, compensatory_date_policy, public_holiday_dates_counted, public_holiday_date_count, weekend_holiday_dates_counted, weekend_holiday_date_count. Formula: planning_workday = Monday_to_Friday AND no named statutory holiday; individual leave is not deducted Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/malta-public-working-days-between with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/malta-public-working-days-between.md

Use this when you need an auditable Mexico 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 article 69 weekly rest is at least one day after six days and the employer/worker schedule is not inferred; sector, state, employer, school and bank calendars are outside scope. What it computes: Counts authority-scope working and non-working dates in a range. Example user requests: Count Mexico working days around Constitution Day observed. 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/mexico-labor-working-days-between with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/mexico-labor-working-days-between.md

Use this when you need an auditable division-specific 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 employer/sector replacement-day rules matter. What it computes: Counts working and non-working dates for a selected Malaysian division over the pinned 2027 schedule. Example user requests: Count Kuala Lumpur working days from 2027-02-01 to 2027-02-15. 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":"2027-02-01","end_date":"2027-02-15","division":"KUL","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, rest_day_policy, substitute_day_policy, calendar_scope, 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/malaysia-working-days-between with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/malaysia-working-days-between.md

Use this when you need an auditable New Zealand 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 regional anniversary or employer-specific closures. What it computes: Counts national working and non-working dates in a New Zealand 2026-2027 range. Example user requests: Count New Zealand working days from 2027-02-01 to 2027-02-15. 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-01","end_date":"2027-02-15","include_start_date":true,"include_end_date":true} Outputs: working_days, non_working_days, public_holidays_counted, territory, territory_name, holiday_names, calendar_scope, regional_anniversary_day_policy, calendar_profile, dataset_version, sources. Formula: for each included date: working_days += New Zealand status.is_working_day Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/new-zealand-working-days-between with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/new-zealand-working-days-between.md

Use this when you need an auditable Nigeria 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 the nationwide federal public-holiday layer, not a universal private-employer, state, local-government, school, banking, market, diplomatic-mission or sector calendar. Ministry of Interior announcements take precedence over conflicting secondary or diplomatic snapshots for federal dates. Eid dates are lunar and can be amended by later official notice. The Public Holidays Act permits special or substituted dates and explicitly does not create an automatic extra day for a holiday falling on Saturday or Sunday; no replacement day is invented here. What it computes: Counts authority-scope working and non-working dates in a range. Example user requests: Count Nigeria working days around Federal Democracy Day. | Count Nigeria working days around Ordinary federal 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-20","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/nigeria-public-working-days-between with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/nigeria-public-working-days-between.md

Use this when you need an auditable Netherlands 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 a public holiday is not automatically a paid day off for every Dutch employee. CAO, employment contract, sector, employer, school, bank and municipal schedules are not inferred; Liberation Day arrangements may be five-year/CAO dependent. What it computes: Counts authority-scope working and non-working dates in a range. Example user requests: Count Netherlands working days around King's Day. | Count Netherlands 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/netherlands-public-working-days-between with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/netherlands-public-working-days-between.md

Use this when you need an auditable Norway 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 full-day list only. Christmas Eve, Easter Eve, Whit Eve, New Year's Eve, collective-agreement, employer, sector, school, bank and local closures are not inferred. Norwegian annual-leave law treats Saturdays separately from Sundays and public holidays; this package uses the declared Monday-Friday business baseline. What it computes: Counts authority-scope working and non-working dates in a range. Example user requests: Count Norway working days around Constitution Day. | Count Norway working days around Christmas Eve is not a full-day 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/norway-public-working-days-between with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/norway-public-working-days-between.md

Use this when you need an auditable Peru 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 choose calendar_scope and workweek explicitly. National holidays and public-sector compensable days have different applicability. This is a declared five-day (Saturday-Sunday rest) or six-day (Sunday rest) planning calendar, not proof of an individual's roster. Essential services, private-employer adoption, compensating shifts, regional holidays, banking, school, tax and procedural deadline calendars require separate evidence. The two compensable public-sector days remain working days for tax purposes. Later decrees require a new snapshot; dates beyond 2026 are unsupported. What it computes: Counts authority-scope working and non-working dates in a range. Required calendar_scope and workweek distinguish national holidays from compensable public-sector days and five/six-day rosters. Example user requests: Peru: National July week. | Peru: Public-sector July week. Inputs: start_date (date); end_date (date); include_start_date (boolean, optional); include_end_date (boolean, optional); calendar_scope (enum); workweek (integer). Complete JSON argument examples: {"start_date":"2026-07-24","end_date":"2026-07-30","calendar_scope":"national_statutory","workweek":5} | {"start_date":"2026-07-24","end_date":"2026-07-30","calendar_scope":"public_sector","workweek":5} 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, calendar_selection, workweek, compensable_day_details. Formula: working day = outside selected weekly rest and selected holiday layer Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/peru-public-working-days-between with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/peru-public-working-days-between.md

Use this when you need an auditable Philippines 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 local-government special holidays, employer schedules and 2027 Eid dates pending a separate proclamation are not inferred. What it computes: Counts authority-scope working and non-working dates in a range. Example user requests: Count Philippines working days around EDSA remains a special working day. | Count Philippines working days around Eid'l Adha is a declared 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/philippines-public-working-days-between with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/philippines-public-working-days-between.md

Use this when you need an auditable Pakistan 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 federal public-holiday layer only. It is not a universal provincial, territory, private-employer, bank, exchange, school, court, diplomatic-mission or sector calendar. Lunar festival dates are pinned to the later federal notifications available for 2026; conflicting exchange or diplomatic calendars are retained as scoped cross-checks and not generalized. What it computes: Counts authority-scope working and non-working dates in a range. Example user requests: Count Pakistan working days around Pakistan Day. | Count Pakistan working days around Ordinary federal 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-05-26","end_date":"2026-05-28","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/pakistan-public-working-days-between with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/pakistan-public-working-days-between.md

Use this when you need an auditable Poland 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. Saturday substitute dates, individual work schedules, employer, sector, school, bank and local schedules are not inferred. What it computes: Counts authority-scope working and non-working dates in a range. Example user requests: Count Poland working days around Christmas Eve. | Count Poland 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/poland-public-working-days-between with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/poland-public-working-days-between.md

Use this when you need an auditable Portugal 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 mandatory nationwide list only. Municipal, autonomous-region, collective-agreement, employer and locally substituted holiday schedules are not inferred. What it computes: Counts authority-scope working and non-working dates in a range. Example user requests: Count Portugal working days around Portugal Day. | Count Portugal 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/portugal-public-working-days-between with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/portugal-public-working-days-between.md

Use this when you need an auditable Romania 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 romania 2026 statutory holiday layer only, with required calendar_basis and work_schedule=mon_fri_planning. The basis selects dates, not a person's identity or religion. No union of Christian calendars, non-Christian additional holidays, public-sector bridge/recovery days, individual rosters, shift exceptions, bank/exchange/school opening, payroll or legal deadlines are computed. Other bases and future years are unsupported. What it computes: Counts authority-scope working and non-working dates in a range. Explicit calendar_basis and mon_fri_planning required; no union of calendars or personal roster inference. Example user requests: Count Romania working days around January 24 remains a statutory holiday even on Saturday. | Count Romania working days around Selected-calendar Good Friday. Inputs: start_date (date); end_date (date); include_start_date (boolean, optional); include_end_date (boolean, optional); calendar_basis (enum); work_schedule (enum). Complete JSON argument examples: {"start_date":"2026-04-09","end_date":"2026-04-14","calendar_basis":"romanian_orthodox","work_schedule":"mon_fri_planning"} | {"start_date":"2026-04-02","end_date":"2026-04-07","calendar_basis":"roman_catholic","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, calendar_basis, work_schedule, is_statutory_holiday, payroll_scope, personal_roster_scope, additional_religious_holidays_scope. Formula: planning_workday = weekday AND no statutory holiday in the explicitly selected calendar_basis Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/romania-public-working-days-between with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/romania-public-working-days-between.md

Use this when you need an auditable Russia 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 federal statutory/public-holiday layer and the Government-published 2026 transfer days over a Saturday-Sunday baseline. Regional holidays, republic/local holidays, employer, bank, school, shift, sector and collective-agreement schedules are not inferred. Future annual transfer resolutions require a refreshed package. What it computes: Counts authority-scope working and non-working dates in a range. Example user requests: Count Russia working days around Russia New Year's holiday. | Count Russia working days around Published transfer day. | Count Russia working days around Ordinary Russia 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-11","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/russia-public-working-days-between with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/russia-public-working-days-between.md

Use this when you need an auditable Saudi Arabia 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 financial-institution scope only. MHRSD business-sector leave, RTGS-specific intervals, government offices, private-employer rosters, Hajj-season branch exceptions and Umm al-Qura forecasts are not inferred. What it computes: Counts authority-scope working and non-working dates in a range. Example user requests: Count Saudi Arabia working days around SAMA Eid Al-Fitr interval. | Count Saudi Arabia working days around Friday/Saturday weekly baseline. | Count Saudi Arabia working days around National Day Saturday substitution. 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-17","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/saudi-financial-working-days-between with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/saudi-financial-working-days-between.md

Use this when you need an auditable Sweden 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. Midsummer Eve, Christmas Eve, New Year's Eve, employer, collective-agreement, sector, school, bank and local closures are not inferred; Sunday is already excluded by the weekday baseline. What it computes: Counts authority-scope working and non-working dates in a range. Example user requests: Count Sweden working days around National Day. | Count Sweden working days around Midsummer Eve is not statutory. 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/sweden-public-working-days-between with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/sweden-public-working-days-between.md

Use this when you need an auditable Slovenia 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 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: Counts authority-scope working and non-working dates in a range. Requires explicit mon_fri_planning; seven named state holidays do not add rest. Example user requests: Count Slovenia working days around Easter Monday is statutory rest. | Count Slovenia working days around Whit Monday is not Whit Sunday. | Count Slovenia working days around Science Day is a state holiday without 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-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_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-days-between with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/slovenia-public-working-days-between.md

Use this when you need an auditable Singapore working-day 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 an employer-specific rest-day roster, bank/exchange closures or future years. What it computes: Counts Singapore working and non-working dates in a 2026-2027 range using MOM public holidays and the CLDR Saturday/Sunday baseline. Example user requests: Count Singapore working days from 2027-02-01 to 2027-02-15. 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-01","end_date":"2027-02-15","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, day_type, holiday_names, holiday_observed, weekend_days, rest_day_policy, calendar_scope, calendar_profile, source_quality, dataset_version, sources. Formula: for each included date: working_days += singapore status.is_working_day Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/singapore-working-days-between with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/singapore-working-days-between.md

Use this when you need an auditable Slovakia 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 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: Counts authority-scope working and non-working dates in a range. Distinguishes 11 rest-day holidays from five named holidays without statutory rest in 2026. Example user requests: Count Slovakia working days around May 8 is a named holiday but a working date. | Count Slovakia working days around Good Friday. | Count Slovakia working days around November 17 is not statutory rest. Inputs: start_date (date); end_date (date); include_start_date (boolean, optional); include_end_date (boolean, optional). Complete JSON argument examples: {"start_date":"2026-05-07","end_date":"2026-05-11"} 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, 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-days-between with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/slovakia-public-working-days-between.md

Use this when you need an auditable South Africa 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, exchange or locally exchanged schedules. What it computes: Counts national working and non-working dates in a South Africa 2026-2027 range. Example user requests: Count South Africa working days from 2026-11-03 to 2026-11-06. Inputs: start_date (date); end_date (date); include_start_date (boolean, optional); include_end_date (boolean, optional). Complete JSON argument examples: {"start_date":"2026-11-03","end_date":"2026-11-06","include_start_date":true,"include_end_date":true} Outputs: working_days, non_working_days, public_holidays_counted, territory, territory_name, holiday_names, calendar_scope, employer_schedule_policy, calendar_profile, dataset_version, sources. Formula: for each included date: working_days += South Africa status.is_working_day Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/south-africa-working-days-between with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/south-africa-working-days-between.md

Use this when you need an auditable Thailand 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 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: Counts authority-scope working and non-working dates in a range. Example user requests: Count Thailand working days around 2027 substitution. | Count Thailand working days around Bangkok-only event remains conditional. Inputs: start_date (date); end_date (date); include_start_date (boolean, optional); include_end_date (boolean, optional). Complete JSON argument examples: {"start_date":"2027-04-13","end_date":"2027-04-15","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/thailand-financial-working-days-between with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/thailand-financial-working-days-between.md

Use this when you need an auditable Türkiye statutory 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 a private employer, school, bank, exchange, local or collective-agreement calendar. What it computes: Counts Türkiye statutory-baseline working and non-working dates over a pinned 2026-2027 range. Example user requests: Count Türkiye working days from 2027-03-01 to 2027-03-31. Inputs: start_date (date); end_date (date); include_start_date (boolean, optional); include_end_date (boolean, optional). Complete JSON argument examples: {"start_date":"2027-03-01","end_date":"2027-03-31","include_start_date":true,"include_end_date":true} Outputs: normalized_start_date, normalized_end_date, working_days, non_working_days, general_holidays_counted, territory, territory_name, 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: for each included date: working_days += Turkey status.is_working_day Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/turkey-working-days-between with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/turkey-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 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: Counts authority-scope working and non-working dates in a range. Example user requests: Count 中国台湾省 working days around Spring Festival substitute holiday. | Count 中国台湾省 working days around Government calendar does not mean private-employer closure. 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-04","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/taiwan-government-working-days-between with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/taiwan-government-working-days-between.md

Use this when you need an auditable UAE federal-government workday count 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 a local-government, private-employer, bank, exchange, school or future-year calendar. What it computes: Counts UAE federal-government working and non-working dates in an exact 2026 range. Example user requests: Count UAE federal-government working days from 2026-08-24 to 2026-08-31. 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-24","end_date":"2026-08-31","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, jurisdiction, day_type, weekend_days, holiday_names, holiday_legal_bases, calendar_scope, private_sector_policy, unresolved_lunar_rules, calendar_profile, dataset_version, sources. Formula: for each included date: working_days += UAE federal status.is_working_day Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/uae-federal-working-days-between with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/uae-federal-working-days-between.md

Use this when you need a 2024-2028 UK SLA, payroll, project or delivery-day count and the selected division's bank holidays must be excluded. 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, a local/employer/market calendar, another jurisdiction or dates outside 2024-2028. What it computes: Counts working and non-working dates in England and Wales, Scotland or Northern Ireland using the official GOV.UK bank-holiday list instead of a weekday-only approximation. Example user requests: How many England and Wales working days are there from 24 December 2026 through 4 January 2027? | Count Northern Ireland business days from 10 to 14 July 2026 inclusive. | How many Scottish working days fall between 1 and 20 June 2026? Inputs: start_date (date); end_date (date); include_start_date (boolean, optional); include_end_date (boolean, optional); division (enum, optional). Complete JSON argument examples: {"start_date":"2026-12-24","end_date":"2027-01-04","include_start_date":true,"include_end_date":true,"division":"england-and-wales"} | {"start_date":"2026-07-10","end_date":"2026-07-14","include_start_date":true,"include_end_date":true,"division":"northern-ireland"} Outputs: division, division_name, normalized_start_date, normalized_end_date, working_days [working days], non_working_days [days], calendar_days_counted [days], bank_holidays_counted, dataset_version, coverage_start, coverage_end, source_snapshot_sha256. 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/uk-working-days-between with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/uk-working-days-between.md

Use this when you need an auditable federal-employee/office working-day 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 a state/local/private-employer/exchange or alternate work-schedule calendar. What it computes: Counts US federal-baseline working and non-working dates using the OPM 2026-2027 schedule. Example user requests: Count US federal working days from 2027-07-01 to 2027-07-10. Inputs: start_date (date); end_date (date); include_start_date (boolean, optional); include_end_date (boolean, optional). Complete JSON argument examples: {"start_date":"2027-07-01","end_date":"2027-07-10","include_start_date":true,"include_end_date":true} Outputs: normalized_start_date, normalized_end_date, working_days, non_working_days, federal_holidays_counted, territory, territory_name, day_type, holiday_names, holiday_observed, holiday_actual_dates, weekend_days, rest_day_policy, calendar_scope, calendar_profile, source_quality, dataset_version, sources. Formula: for each included date: working_days += US federal status.is_working_day Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/us-federal-working-days-between with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/us-federal-working-days-between.md

Use this when you need an auditable nationwide count with explicit workweek 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 workweek or employer/shift scope is unknown. What it computes: Counts working and non-working dates in Uzbekistan's pinned 2026 schedule for a required workweek variant. Example user requests: Count five-day Uzbekistan working days from 2026-05-25 to 2026-06-02. Inputs: start_date (date); end_date (date); workweek (integer); include_start_date (boolean, optional); include_end_date (boolean, optional). Complete JSON argument examples: {"start_date":"2026-05-25","end_date":"2026-06-02","workweek":5,"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, 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: for each included date: working_days += status.is_working_day Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/uzbekistan-working-days-between with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/uzbekistan-working-days-between.md

Use this when you need an auditable Vietnam 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 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: Counts authority-scope working and non-working dates in a range. Example user requests: Count Vietnam working days around New Year transfer. | Count Vietnam working days around Vietnam Cultural 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-26","end_date":"2026-05-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/vietnam-public-working-days-between with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/vietnam-public-working-days-between.md

Use this when you want to know how long an EV needs on a home wallbox, a public AC post or a DC fast charger to reach a target charge, or what the session costs at a given electricity price. 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 battery's charge time from ampere-hours and charger current (use battery-charge-time) or the driving range the added energy gives (use ev-range-efficiency); DC fast charging above about 80 % tapers strongly and takes longer than this constant-power estimate. What it computes: Estimates how long an electric vehicle takes to charge between two states of charge from its battery capacity, the charger power (capped by the onboard charger for AC charging) and the charging efficiency, plus the energy drawn from the grid and its cost. Inputs: battery_capacity_kwh (number, kWh); start_percent (number, %, optional); target_percent (number, %, optional); charger_power_kw (number, kW); max_onboard_charger_kw (number, kW, optional); charging_efficiency_percent (number, %, optional); electricity_price_per_kwh (number, per kWh, optional). Complete JSON argument examples: {"battery_capacity_kwh":75,"start_percent":20,"target_percent":80,"charger_power_kw":7,"charging_efficiency_percent":90,"electricity_price_per_kwh":0.3} | {"battery_capacity_kwh":60,"start_percent":10,"target_percent":100,"charger_power_kw":11,"max_onboard_charger_kw":7.4} Outputs: energy_added_kwh [kWh], energy_from_grid_kwh [kWh], effective_power_kw [kW], charging_time_hours [h], charging_time_text, cost, range_note. Formula: energy_added_kwh = battery_capacity_kwh × (target_percent − start_percent) / 100; energy_from_grid_kwh = energy_added_kwh / (charging_efficiency_percent / 100); effective_power_kw = min(charger_power_kw, max_onboard_charger_kw); charging_time_hours = energy_from_grid_kwh / effective_power_kw; cost = energy_from_grid_kwh × electricity_price_per_kwh Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/ev-charging-time with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/energy/ev-charging-time.md

Use this when you need someone's Chinese zodiac sign and element from a Gregorian birth date, especially for January–February births where the boundary matters, or the sign's traditional compatibility groups. 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 full Bazi chart with month, day and hour pillars (use bazi-four-pillars), or the Western star sign (use zodiac). What it computes: Finds the Chinese zodiac animal (生肖 shengxiao), sexagenary year (干支 ganzhi), stem element, yin/yang, nayin (纳音) and fixed element for a birth date, using either the Chinese New Year boundary or the 立春 (Lichun) boundary, plus the traditional relationship groups (六合, 三合, 六冲, 六害, 相刑) and 本命年 years. Inputs: birth_date (date); boundary (enum, optional); reference_year (integer, optional). Complete JSON argument examples: {"birth_date":"1990-02-10","boundary":"lunar_new_year","reference_year":2026} | {"birth_date":"1990-02-03","boundary":"lichun"} Outputs: zodiac, zodiac_cn, year_ganzhi, year_ganzhi_pinyin, year_english, stem_element, yin_yang, nayin, animal_fixed_element, year_used, chinese_new_year_date, lichun_datetime, boundary_note, benmingnian_years, secret_friend, trine_partners, clash, harm, punishment, age_in_reference_year [years], is_benmingnian_in_reference_year, reference_year_zodiac. Formula: year_used = Gregorian year, minus 1 when birth_date is before Chinese New Year (or before 立春 with boundary = lichun); ganzhi index = (year_used − 4) mod 60; animal = branch = index mod 12; 六合 partner = (13 − b) mod 12; 三合 = b ± 4; 六冲 = b + 6; 六害 partner = (7 − b) mod 12 Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/chinese-zodiac with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/lunar/chinese-zodiac.md

Use this only after search_calculators when its input_hints do not resolve a range, enum or optional-field question. Return the full input/output schema, formula, sources, examples and limitations for one calculator. Do not call it when the search result already supplies enough input detail; call run_calculator instead. This tool only describes and does not calculate.

List the calculator categories with id, name, description and calculator count. Use it to orient before list_calculators. Does not perform calculations.

List all calculators, optionally filtered by category id (finance, health, fitness, math, geometry, statistics, conversion, physics, chemistry, everyday, food, construction, business, time, medical, engineering, weather, investing, developer, energy, photography, science, gaming, lunar, yijing). Returns calculator_id, name, description, use_when and required inputs for each. Use it to browse a whole category; use search_calculators for keyword lookup. Does not perform calculations.

Use this when you need the date or time of 立春, 清明, 夏至, 冬至 or any other solar term in a given year, or the full 24-term table. 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 only need the term that a specific date falls in (use lunar-calendar-converter), or you need sunrise/sunset times (use sunrise-sunset). What it computes: Lists the 24 solar terms (节气 jieqi) of a Gregorian year with their exact instants: the moments the Sun's apparent longitude reaches multiples of 15°, computed astronomically and shown in a chosen UTC offset (China Standard Time by default). Example user requests: List all 24 solar terms for 2027 in UTC+8. | 2026 年立春和冬至的准确时间是什么？ | When is Qingming this year in China Standard Time? Inputs: year (integer); utc_offset_hours (number, h, optional). Complete JSON argument examples: {"year":2024,"utc_offset_hours":8} | {"year":2026,"utc_offset_hours":8} Outputs: terms, lichun_date, spring_equinox, summer_solstice, autumn_equinox, winter_solstice, year_ganzhi, suishou_note, utc_offset. Formula: term instant: apparent geocentric solar longitude λ(JDE) = k·15° for k = 0 (春分) … 23 (惊蛰), solved by Newton iteration; UT = TT − ΔT; local time = UT + utc_offset_hours Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/solar-terms with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/lunar/solar-terms.md

Use this when you need the next or historical daylight-saving/offset changes for scheduling, payroll, travel, audits or a regression test, with a specific reproducible tzdb version. 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 only need to convert one ordinary date-time, need legal advice about a jurisdiction's time law, or need changes announced after this pinned release. What it computes: Lists every UTC-offset transition for one IANA zone and date range using pinned tzdb 2026d, including the local boundaries, offsets, abbreviations and whether the clock creates a gap or overlap. Example user requests: List every 2026 UTC-offset transition in America/New_York with local boundaries. | When does Australia/Adelaide change clocks between 2026-01-01 and 2027-01-01? | 列出 Europe/London 在 2026 年的夏令时转换点、前后偏移和 IANA 数据版本。 Inputs: time_zone (string); start_date (date); end_date (date). Complete JSON argument examples: {"time_zone":"America/New_York","start_date":"2026-01-01","end_date":"2026-12-31"} Outputs: time_zone, resolved_zone_id, start_date, end_date, transition_count, transitions, tzdb_version, dataset_version, source_url, source_sha256, coverage_note. Formula: select zone transition instants whose local boundary before or after lies inside [start_date, end_date] Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/time-zone-transitions with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/time/time-zone-transitions.md

List every unit symbol supported by convert_units, grouped by quantity, with names. Use it when a unit symbol is rejected with UNKNOWN_UNIT. Does not convert anything.

Use this before a working-day or business-day task to select the correct evidence package. It distinguishes the worldwide CLDR weekday/weekend baseline, the broad source-labelled OpenWorkdays national-scope reference, the clearly labelled OpenHolidays nationwide public-holiday reference, and the official public-holiday calendars for mainland China, Singapore, Australia, the US, Canada, Japan, India's central government, UAE federal government, New Zealand, South Africa, Ireland plus the UK. The result contains one machine-readable route per CLDR territory, or one route when the optional territory filter is supplied, including whether holiday semantics are unsupported, reference-only, or require a jurisdiction-specific input such as the UK division, Australian state/territory or Indian office scope. US is OPM federal scope only; CA is Canada Labour Code federally regulated-employer scope and does not infer substitute days; JP is statutory national holidays only and does not infer employer closures; IN preserves Gazetted/Restricted classes and does not infer state/UT or local optional selections; AE is UAE federal-government scope with exact 2026 dates only and does not infer local/private schedules or unresolved lunar dates; NZ is national statutory dates only and does not infer regional anniversary days; ZA is national public holidays over a Monday-Friday baseline and does not infer employer holiday exchanges; IE excludes Good Friday and does not infer next-working-day closures for weekend holidays. This is read-only catalogue discovery; it does not calculate a date or count and must not be reported as a calculation success.

Use this when you need to identify or describe a hexagram, convert between its number, name, trigram pair and line pattern, or find its derived hexagrams and palace position. 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 have moving lines and need the changed hexagram and reading rule (use hexagram-change), or you need to cast a hexagram from a date or numbers (use meihua-yishu). What it computes: Identifies one of the 64 hexagrams (六十四卦, liushisi gua) from its King Wen number, name, two trigrams or line digits and returns its lines, trigrams, nuclear (互卦, hugua), inverse (综卦, zonggua) and opposite (错卦, cuogua) hexagrams, its Jing Fang palace (京房八宫, Jingfang bagong) with 世/应 (shi/ying) lines, and the received judgment text (卦辞, guaci). Inputs: king_wen_number (integer, optional); name (string, optional); upper_trigram (string, optional); lower_trigram (string, optional); lines (string, optional). Valid input combinations: Identify the hexagram with king_wen_number, name, lines, or the complete upper_trigram + lower_trigram pair. Multiple identification methods may be supplied when they agree. Complete JSON argument examples: {"king_wen_number":1} | {"lines":"100010"} Outputs: number, name_cn, full_name_cn, pinyin, english, symbol, lines, lines_text, upper_trigram, lower_trigram, nuclear_hexagram, inverse_hexagram, opposite_hexagram, palace, palace_position, shi_line, ying_line, judgment_text, sequence_pair, binary_value, notes. Formula: lower trigram = lines 1–3, upper trigram = lines 4–6; nuclear = lines 2,3,4 + 3,4,5; inverse = reversed line order; opposite = each line flipped; binary_value = Σ line_i · 2^(i−1); 应 = 世 ± 3 Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/hexagram-lookup with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/yijing/hexagram-lookup.md

Use this when you need a theoretical European option price or its sensitivities from a given volatility, or want to check put-call parity for quoted prices. 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 option is American with early exercise value, the underlying pays discrete dividends, or you need implied volatility from a market price (solve numerically instead). Informational only; not financial advice. What it computes: Prices a European call and put with the Black-Scholes-Merton formula from spot, strike, time to expiry, risk-free rate, volatility and a continuous dividend yield, and reports d1, d2 and the Greeks (delta, gamma, vega, theta, rho). Inputs: spot_price (number); strike_price (number); time_years (number, years); risk_free_rate_percent (number, % per year); volatility_percent (number, % per year); dividend_yield_percent (number, % per year, optional). Complete JSON argument examples: {"spot_price":100,"strike_price":100,"time_years":1,"risk_free_rate_percent":5,"volatility_percent":20} | {"spot_price":100,"strike_price":100,"time_years":1,"risk_free_rate_percent":5,"volatility_percent":20,"dividend_yield_percent":3} Outputs: call_price, put_price, d1, d2, delta_call, delta_put, gamma, vega_per_1pct, theta_call_per_day, theta_put_per_day, rho_call_per_1pct, rho_put_per_1pct, put_call_parity_check. Formula: d1 = [ln(S/K) + (r − q + σ²/2)·T] / (σ·√T); d2 = d1 − σ·√T; C = S·e^(−qT)·N(d1) − K·e^(−rT)·N(d2); P = K·e^(−rT)·N(−d2) − S·e^(−qT)·N(−d1); Δ_call = e^(−qT)·N(d1); Γ = e^(−qT)·φ(d1)/(S·σ·√T); vega = S·e^(−qT)·φ(d1)·√T; Θ_call = −S·e^(−qT)·φ(d1)·σ/(2√T) − r·K·e^(−rT)·N(d2) + q·S·e^(−qT)·N(d1); ρ_call = K·T·e^(−rT)·N(d2), with r, q, σ as decimals Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/black-scholes with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/investing/black-scholes.md

Use this when you must safely turn a named-zone local time into an instant, validate a scheduled time around a daylight-saving transition, or preserve every possible interpretation instead of silently choosing one. 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 input already includes a numeric UTC offset or Z, the task only needs the current clock time, or latitude/longitude must first be mapped to a zone. What it computes: Resolves a local wall-clock time with pinned IANA tzdb 2026d. Returns every valid UTC candidate for a repeated fall-back time, or the exact gap and shift-forward suggestion for a nonexistent spring-forward time. Example user requests: Resolve 2026-11-01 01:30 in America/New_York and return both UTC candidates. | Does 2026-03-08 02:30 exist in New York? Show the DST gap. | 判断 Australia/Adelaide 的 2026-10-04 02:30 是否存在，并给出时区数据版本。 Inputs: local_datetime (string); time_zone (string). Complete JSON argument examples: {"local_datetime":"2026-11-01T01:30:00","time_zone":"America/New_York"} | {"local_datetime":"2026-03-08T02:30:00","time_zone":"America/New_York"} Outputs: local_datetime, time_zone, resolved_zone_id, status, candidate_count, candidates, gap, related_transition, previous_transition, next_transition, tzdb_version, dataset_version, source_url, source_sha256, coverage_note. Formula: for each zone offset o: candidate_utc = local_wall_time + o; keep candidates whose active offset at candidate_utc equals o Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/local-time-resolver with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/time/local-time-resolver.md

Use this when the user needs one of Calcgrid's 737 deterministic calculators and no dedicated typed tool covers it. Call it immediately after search_calculators once calculator_id and input_hints are known; do not stop at search or schema discovery. Do not use it for trivial arithmetic, live rates or unrelated tasks. Returns typed values with units, formula, sources, freshness and timestamp; validation errors identify the field and a repair hint.