com.tttkmbb/calcgrid

Est-ce que com.tttkmbb/calcgrid est sûr ?

Au dernier audit MCP Hub, le serveur MCP « com.tttkmbb/calcgrid » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 253 outils

• add_ar_working_days≈ 1308 tokens

  Use this when you need a deterministic Argentina working-day offset. 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: Adds or subtracts Argentina authority-scope working days in exact coverage. Example user requests: Add or subtract Argentina working days around Argentina national holiday. Inputs: start_date (date); working_days (integer). Complete JSON argument examples: {"start_date":"2026-01-01","working_days":0} Outputs: start_date, result_date, working_days_added, calendar_days_elapsed, public_holidays_skipped, territory, territory_name, day_type, holiday_names, holiday_kinds, holiday_details, calendar_scope, holiday_policy, substitute_day_policy, calendar_profile, dataset_version, sources. Formula: move one day at a time; decrement only on status.is_working_day=true Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/argentina-add-working-days with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/argentina-add-working-days.md

  Paramètres, retour & exemple (2)

  Paramètres

  • start_date · string · requis
    Gregorian start date in 2026-2026.
  • working_days · integer · requis
    Signed offset; start date excluded for non-zero offsets.

  Exemple d'appel

  {"name": "add_ar_working_days", "arguments": {"start_date": "texte", "working_days": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• add_at_working_days≈ 1336 tokens

  Use this when you need a deterministic Austria working-day offset. 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: Adds or subtracts Austria authority-scope working days in exact coverage. Example user requests: Add or subtract Austria working days around Austrian National Day. | Add or subtract Austria working days around Ordinary weekday. Inputs: start_date (date); working_days (integer). Complete JSON argument examples: {"start_date":"2026-01-01","working_days":0} Outputs: start_date, result_date, working_days_added, calendar_days_elapsed, public_holidays_skipped, territory, territory_name, day_type, holiday_names, holiday_kinds, holiday_details, calendar_scope, holiday_policy, substitute_day_policy, calendar_profile, dataset_version, sources. Formula: move one day at a time; decrement only on status.is_working_day=true Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/austria-public-add-working-days with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/austria-public-add-working-days.md

  Paramètres, retour & exemple (2)

  Paramètres

  • start_date · string · requis
    Gregorian start date in 2026-2027.
  • working_days · integer · requis
    Signed offset; start date excluded for non-zero offsets.

  Exemple d'appel

  {"name": "add_at_working_days", "arguments": {"start_date": "texte", "working_days": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• add_australia_working_days≈ 1450 tokens

  Use this when you need a state/territory-specific Australian date offset in 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 the division is unknown or the task needs local, employer, exchange or future-year rules. What it computes: Adds or subtracts working days using the selected Australian state/territory public-holiday calendar. Example user requests: Add five NSW working days after 2026-04-24. Inputs: start_date (date); division (enum); working_days (integer). Complete JSON argument examples: {"start_date":"2026-04-24","division":"nsw","working_days":5} Outputs: start_date, result_date, working_days_added, calendar_days_elapsed, public_holidays_skipped, 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: move one day at a time; decrement remaining only when selected status.is_working_day=true Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/australia-add-working-days with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/australia-add-working-days.md

  Paramètres, retour & exemple (3)

  Paramètres

  • division · string · requis · act | nsw | nt | qld | sa | tas | vic | wa
    Required Australian state/territory code: act, nsw, nt, qld, sa, tas, vic or wa.
  • start_date · string · requis
    Gregorian start date in 2026-2027.
  • working_days · integer · requis
    Signed offset; start date is excluded for non-zero offsets.

  Exemple d'appel

  {"name": "add_australia_working_days", "arguments": {"division": "act", "start_date": "texte", "working_days": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• add_bd_working_days≈ 1355 tokens

  Use this when you need a deterministic Bangladesh working-day offset. 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: Adds or subtracts Bangladesh authority-scope working days in exact coverage. Example user requests: Add or subtract Bangladesh working days around Election-period special holiday. | Add or subtract Bangladesh working days around Eid-ul-Adha period. Inputs: start_date (date); working_days (integer). Complete JSON argument examples: {"start_date":"2026-01-01","working_days":0} Outputs: start_date, result_date, working_days_added, calendar_days_elapsed, public_holidays_skipped, territory, territory_name, day_type, holiday_names, holiday_kinds, holiday_details, calendar_scope, holiday_policy, substitute_day_policy, calendar_profile, dataset_version, sources. Formula: move one day at a time; decrement only on status.is_working_day=true Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/bangladesh-public-add-working-days with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/bangladesh-public-add-working-days.md

  Paramètres, retour & exemple (2)

  Paramètres

  • start_date · string · requis
    Gregorian start date in 2026-2026.
  • working_days · integer · requis
    Signed offset; start date excluded for non-zero offsets.

  Exemple d'appel

  {"name": "add_bd_working_days", "arguments": {"start_date": "texte", "working_days": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• add_be_working_days≈ 1346 tokens

  Use this when you need a deterministic Belgium working-day offset. 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: Adds or subtracts Belgium authority-scope working days in exact coverage. Example user requests: Add or subtract Belgium working days around Belgian National Day. | Add or subtract Belgium working days around Ordinary weekday. Inputs: start_date (date); working_days (integer). Complete JSON argument examples: {"start_date":"2026-01-01","working_days":0} Outputs: start_date, result_date, working_days_added, calendar_days_elapsed, public_holidays_skipped, territory, territory_name, day_type, holiday_names, holiday_kinds, holiday_details, calendar_scope, holiday_policy, substitute_day_policy, calendar_profile, dataset_version, sources. Formula: move one day at a time; decrement only on status.is_working_day=true Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/belgium-public-add-working-days with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/belgium-public-add-working-days.md

  Paramètres, retour & exemple (2)

  Paramètres

  • start_date · string · requis
    Gregorian start date in 2026-2027.
  • working_days · integer · requis
    Signed offset; start date excluded for non-zero offsets.

  Exemple d'appel

  {"name": "add_be_working_days", "arguments": {"start_date": "texte", "working_days": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• add_bg_working_days≈ 1773 tokens

  Use this when you need a deterministic Bulgaria working-day offset. 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: Adds or subtracts Bulgaria authority-scope working days in exact coverage. Requires explicit mon_fri_planning; education-only holidays do not create general rest. Example user requests: Add or subtract Bulgaria working days around One-off euro transition rest, not statutory holiday. | Add or subtract Bulgaria working days around May 24 Sunday replacement. | Add or subtract Bulgaria working days around No nationwide school-holiday substitute. Inputs: start_date (date); working_days (integer); work_schedule (enum). Complete JSON argument examples: {"start_date":"2026-01-01","working_days":0,"work_schedule":"mon_fri_planning"} Outputs: start_date, result_date, working_days_added, calendar_days_elapsed, public_holidays_skipped, 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-add-working-days with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/bulgaria-public-add-working-days.md

  Paramètres, retour & exemple (3)

  Paramètres

  • start_date · string · requis
    Gregorian start date in 2026-2026.
  • working_days · integer · requis
    Signed offset; start date excluded for non-zero offsets.
  • work_schedule · string · requis · mon_fri_planning
    Required explicit Monday-Friday planning baseline, not a universal legal roster.

  Exemple d'appel

  {"name": "add_bg_working_days", "arguments": {"start_date": "texte", "working_days": 1, "work_schedule": "mon_fri_planning"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• add_br_working_days≈ 1271 tokens

  Use this when you need a deterministic Brazil working-day offset. 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: Adds or subtracts Brazil authority-scope working days in exact coverage. Example user requests: Add or subtract Brazil working days around Tiradentes. Inputs: start_date (date); working_days (integer). Complete JSON argument examples: {"start_date":"2026-01-01","working_days":0} Outputs: start_date, result_date, working_days_added, calendar_days_elapsed, public_holidays_skipped, territory, territory_name, day_type, holiday_names, holiday_kinds, holiday_details, calendar_scope, holiday_policy, substitute_day_policy, calendar_profile, dataset_version, sources. Formula: move one day at a time; decrement only on status.is_working_day=true Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/brazil-federal-add-working-days with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/brazil-federal-add-working-days.md

  Paramètres, retour & exemple (2)

  Paramètres

  • start_date · string · requis
    Gregorian start date in 2026-2026.
  • working_days · integer · requis
    Signed offset; start date excluded for non-zero offsets.

  Exemple d'appel

  {"name": "add_br_working_days", "arguments": {"start_date": "texte", "working_days": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• add_canada_federal_working_days≈ 1320 tokens

  Use this when you need a deterministic baseline offset for a federally regulated-employer calendar in 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 provincial, private-employer or schedule-specific substitution result. What it computes: Adds or subtracts dates using Canada federal general holidays and a Saturday/Sunday baseline; schedule-dependent substitute days remain unresolved. Example user requests: Add five Canada federal working days after 2026-09-28. Inputs: start_date (date); working_days (integer). Complete JSON argument examples: {"start_date":"2026-09-29","working_days":1} Outputs: start_date, result_date, working_days_added, calendar_days_elapsed, federal_general_holidays_skipped, 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: move one day at a time; decrement remaining only when Canada federal status.is_working_day=true Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/canada-federal-add-working-days with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/canada-federal-add-working-days.md

  Paramètres, retour & exemple (2)

  Paramètres

  • start_date · string · requis
    Gregorian start date in 2026-2027.
  • working_days · integer · requis
    Signed offset; start date is excluded for non-zero offsets.

  Exemple d'appel

  {"name": "add_canada_federal_working_days", "arguments": {"start_date": "texte", "working_days": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• add_ch_working_days≈ 1310 tokens

  Use this when you need a deterministic Switzerland working-day offset. 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: Adds or subtracts Switzerland authority-scope working days in exact coverage. Example user requests: Add or subtract Switzerland working days around Swiss National Day. | Add or subtract Switzerland working days around Cantonal holiday is not inferred. Inputs: start_date (date); working_days (integer). Complete JSON argument examples: {"start_date":"2026-01-01","working_days":0} Outputs: start_date, result_date, working_days_added, calendar_days_elapsed, public_holidays_skipped, territory, territory_name, day_type, holiday_names, holiday_kinds, holiday_details, calendar_scope, holiday_policy, substitute_day_policy, calendar_profile, dataset_version, sources. Formula: move one day at a time; decrement only on status.is_working_day=true Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/switzerland-public-add-working-days with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/switzerland-public-add-working-days.md

  Paramètres, retour & exemple (2)

  Paramètres

  • start_date · string · requis
    Gregorian start date in 2026-2027.
  • working_days · integer · requis
    Signed offset; start date excluded for non-zero offsets.

  Exemple d'appel

  {"name": "add_ch_working_days", "arguments": {"start_date": "texte", "working_days": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• add_china_working_days≈ 1348 tokens

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

  Paramètres, retour & exemple (2)

  Paramètres

  • start_date · string · requis
    Starting mainland China civil date (YYYY-MM-DD), within 2024-2026.
  • working_days · integer · requis
    Signed number of official working days to add; the start date is excluded when non-zero. Negative values move backward. Unit: working days.

  Exemple d'appel

  {"name": "add_china_working_days", "arguments": {"start_date": "texte", "working_days": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• add_cl_working_days≈ 1354 tokens

  Use this when you need a deterministic Chile working-day offset. 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: Adds or subtracts Chile authority-scope working days in exact coverage. Example user requests: Add or subtract Chile working days around Chile Labour Day. | Add or subtract Chile working days around Chile ordinary working day. | Add or subtract Chile working days around Chile winter-solstice Indigenous Peoples Day. Inputs: start_date (date); working_days (integer). Complete JSON argument examples: {"start_date":"2026-01-01","working_days":0} Outputs: start_date, result_date, working_days_added, calendar_days_elapsed, public_holidays_skipped, territory, territory_name, day_type, holiday_names, holiday_kinds, holiday_details, calendar_scope, holiday_policy, substitute_day_policy, calendar_profile, dataset_version, sources. Formula: move one day at a time; decrement only on status.is_working_day=true Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/chile-public-add-working-days with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/chile-public-add-working-days.md

  Paramètres, retour & exemple (2)

  Paramètres

  • start_date · string · requis
    Gregorian start date in 2026-2026.
  • working_days · integer · requis
    Signed offset; start date excluded for non-zero offsets.

  Exemple d'appel

  {"name": "add_cl_working_days", "arguments": {"start_date": "texte", "working_days": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• add_co_working_days≈ 1338 tokens

  Use this when you need a deterministic Colombia working-day offset. 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: Adds or subtracts Colombia authority-scope working days in exact coverage. Example user requests: Add or subtract Colombia working days around Colombia transferred Three Kings holiday. | Add or subtract Colombia working days around Colombia Good Friday. | Add or subtract Colombia working days around Ordinary Colombia working day. Inputs: start_date (date); working_days (integer). Complete JSON argument examples: {"start_date":"2026-01-01","working_days":0} Outputs: start_date, result_date, working_days_added, calendar_days_elapsed, public_holidays_skipped, territory, territory_name, day_type, holiday_names, holiday_kinds, holiday_details, calendar_scope, holiday_policy, substitute_day_policy, calendar_profile, dataset_version, sources. Formula: move one day at a time; decrement only on status.is_working_day=true Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/colombia-public-add-working-days with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/colombia-public-add-working-days.md

  Paramètres, retour & exemple (2)

  Paramètres

  • start_date · string · requis
    Gregorian start date in 2026-2026.
  • working_days · integer · requis
    Signed offset; start date excluded for non-zero offsets.

  Exemple d'appel

  {"name": "add_co_working_days", "arguments": {"start_date": "texte", "working_days": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• add_cz_working_days≈ 1669 tokens

  Use this when you need a deterministic Czech Republic working-day offset. 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: Adds or subtracts Czech Republic authority-scope working days in exact coverage. Requires explicit mon_fri_planning; commemorative events do not create rest. Example user requests: Add or subtract Czech Republic working days around Two names on January 1, one rest date. | Add or subtract Czech Republic working days around Education commemorative day remains a planning workday. | Add or subtract Czech Republic working days around November 17 is a Czech statutory rest day. Inputs: start_date (date); working_days (integer); work_schedule (enum). Complete JSON argument examples: {"start_date":"2026-01-01","working_days":0,"work_schedule":"mon_fri_planning"} Outputs: start_date, result_date, working_days_added, calendar_days_elapsed, public_holidays_skipped, 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-add-working-days with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/czech-public-add-working-days.md

  Paramètres, retour & exemple (3)

  Paramètres

  • start_date · string · requis
    Gregorian start date in 2026-2026.
  • working_days · integer · requis
    Signed offset; start date excluded for non-zero offsets.
  • work_schedule · string · requis · mon_fri_planning
    Required explicit Monday-Friday planning baseline, not a statutory universal roster.

  Exemple d'appel

  {"name": "add_cz_working_days", "arguments": {"start_date": "texte", "working_days": 1, "work_schedule": "mon_fri_planning"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• add_de_working_days≈ 1289 tokens

  Use this when you need a deterministic Germany working-day offset. 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: Adds or subtracts Germany authority-scope working days in exact coverage. Example user requests: Add or subtract Germany working days around German Unity Day. | Add or subtract Germany working days around Ordinary weekday. Inputs: start_date (date); working_days (integer). Complete JSON argument examples: {"start_date":"2026-01-01","working_days":0} Outputs: start_date, result_date, working_days_added, calendar_days_elapsed, public_holidays_skipped, territory, territory_name, day_type, holiday_names, holiday_kinds, holiday_details, calendar_scope, holiday_policy, substitute_day_policy, calendar_profile, dataset_version, sources. Formula: move one day at a time; decrement only on status.is_working_day=true Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/germany-national-add-working-days with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/germany-national-add-working-days.md

  Paramètres, retour & exemple (2)

  Paramètres

  • start_date · string · requis
    Gregorian start date in 2026-2026.
  • working_days · integer · requis
    Signed offset; start date excluded for non-zero offsets.

  Exemple d'appel

  {"name": "add_de_working_days", "arguments": {"start_date": "texte", "working_days": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• add_dk_working_days≈ 1318 tokens

  Use this when you need a deterministic Denmark working-day offset. 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: Adds or subtracts Denmark authority-scope working days in exact coverage. Example user requests: Add or subtract Denmark working days around Ascension Day. | Add or subtract Denmark working days around Constitution Day is not a statutory holiday. Inputs: start_date (date); working_days (integer). Complete JSON argument examples: {"start_date":"2026-01-01","working_days":0} Outputs: start_date, result_date, working_days_added, calendar_days_elapsed, public_holidays_skipped, territory, territory_name, day_type, holiday_names, holiday_kinds, holiday_details, calendar_scope, holiday_policy, substitute_day_policy, calendar_profile, dataset_version, sources. Formula: move one day at a time; decrement only on status.is_working_day=true Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/denmark-public-add-working-days with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/denmark-public-add-working-days.md

  Paramètres, retour & exemple (2)

  Paramètres

  • start_date · string · requis
    Gregorian start date in 2026-2027.
  • working_days · integer · requis
    Signed offset; start date excluded for non-zero offsets.

  Exemple d'appel

  {"name": "add_dk_working_days", "arguments": {"start_date": "texte", "working_days": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• add_ee_working_days≈ 1849 tokens

  Use this when you need a deterministic Estonia working-day offset. 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: Adds or subtracts Estonia authority-scope working days in exact coverage. Requires explicit mon_fri_planning; national-importance dates and three-hour shortening never add full-day rest. Example user requests: Add or subtract Estonia working days around Independence Day is statutory rest. | Add or subtract Estonia working days around Shortened working date is not full-day rest. | Add or subtract Estonia working days around National importance does not imply rest. Inputs: start_date (date); working_days (integer); work_schedule (enum). Complete JSON argument examples: {"start_date":"2026-01-01","working_days":0,"work_schedule":"mon_fri_planning"} Outputs: start_date, result_date, working_days_added, calendar_days_elapsed, public_holidays_skipped, 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. 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-add-working-days with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/estonia-public-add-working-days.md

  Paramètres, retour & exemple (3)

  Paramètres

  • start_date · string · requis
    Gregorian start date in 2026-2026.
  • working_days · integer · requis
    Signed offset; start date excluded for non-zero offsets.
  • work_schedule · string · requis · mon_fri_planning
    Required explicit Monday-Friday planning baseline; not an individual legal roster.

  Exemple d'appel

  {"name": "add_ee_working_days", "arguments": {"start_date": "texte", "working_days": 1, "work_schedule": "mon_fri_planning"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• add_eg_working_days≈ 1379 tokens

  Use this when you need a deterministic Egypt working-day offset. 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: Adds or subtracts Egypt authority-scope working days in exact coverage. Example user requests: Add or subtract Egypt working days around Eid al-Fitr public holiday. | Add or subtract Egypt working days around Ordinary Egypt working day. Inputs: start_date (date); working_days (integer). Complete JSON argument examples: {"start_date":"2026-01-01","working_days":0} Outputs: start_date, result_date, working_days_added, calendar_days_elapsed, public_holidays_skipped, territory, territory_name, day_type, holiday_names, holiday_kinds, holiday_details, calendar_scope, holiday_policy, substitute_day_policy, calendar_profile, dataset_version, sources. Formula: move one day at a time; decrement only on status.is_working_day=true Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/egypt-public-add-working-days with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/egypt-public-add-working-days.md

  Paramètres, retour & exemple (2)

  Paramètres

  • start_date · string · requis
    Gregorian start date in 2026-2026.
  • working_days · integer · requis
    Signed offset; start date excluded for non-zero offsets.

  Exemple d'appel

  {"name": "add_eg_working_days", "arguments": {"start_date": "texte", "working_days": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• add_es_working_days≈ 1290 tokens

  Use this when you need a deterministic Spain working-day offset. 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: Adds or subtracts Spain authority-scope working days in exact coverage. Example user requests: Add or subtract Spain working days around National Day. | Add or subtract Spain working days around Ordinary weekday. Inputs: start_date (date); working_days (integer). Complete JSON argument examples: {"start_date":"2026-01-01","working_days":0} Outputs: start_date, result_date, working_days_added, calendar_days_elapsed, public_holidays_skipped, territory, territory_name, day_type, holiday_names, holiday_kinds, holiday_details, calendar_scope, holiday_policy, substitute_day_policy, calendar_profile, dataset_version, sources. Formula: move one day at a time; decrement only on status.is_working_day=true Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/spain-national-add-working-days with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/spain-national-add-working-days.md

  Paramètres, retour & exemple (2)

  Paramètres

  • start_date · string · requis
    Gregorian start date in 2026-2026.
  • working_days · integer · requis
    Signed offset; start date excluded for non-zero offsets.

  Exemple d'appel

  {"name": "add_es_working_days", "arguments": {"start_date": "texte", "working_days": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• add_fi_working_days≈ 1354 tokens

  Use this when you need a deterministic Finland working-day offset. 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: Adds or subtracts Finland authority-scope working days in exact coverage. Example user requests: Add or subtract Finland working days around Independence Day. | Add or subtract Finland working days around Midsummer Eve is agreement-dependent. Inputs: start_date (date); working_days (integer). Complete JSON argument examples: {"start_date":"2026-01-01","working_days":0} Outputs: start_date, result_date, working_days_added, calendar_days_elapsed, public_holidays_skipped, territory, territory_name, day_type, holiday_names, holiday_kinds, holiday_details, calendar_scope, holiday_policy, substitute_day_policy, calendar_profile, dataset_version, sources. Formula: move one day at a time; decrement only on status.is_working_day=true Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/finland-public-add-working-days with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/finland-public-add-working-days.md

  Paramètres, retour & exemple (2)

  Paramètres

  • start_date · string · requis
    Gregorian start date in 2026-2027.
  • working_days · integer · requis
    Signed offset; start date excluded for non-zero offsets.

  Exemple d'appel

  {"name": "add_fi_working_days", "arguments": {"start_date": "texte", "working_days": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• add_fr_working_days≈ 1275 tokens

  Use this when you need a deterministic France working-day offset. 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: Adds or subtracts France authority-scope working days in exact coverage. Example user requests: Add or subtract France working days around Bastille Day. Inputs: start_date (date); working_days (integer). Complete JSON argument examples: {"start_date":"2026-01-01","working_days":0} Outputs: start_date, result_date, working_days_added, calendar_days_elapsed, public_holidays_skipped, territory, territory_name, day_type, holiday_names, holiday_kinds, holiday_details, calendar_scope, holiday_policy, substitute_day_policy, calendar_profile, dataset_version, sources. Formula: move one day at a time; decrement only on status.is_working_day=true Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/france-add-working-days with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/france-add-working-days.md

  Paramètres, retour & exemple (2)

  Paramètres

  • start_date · string · requis
    Gregorian start date in 2026-2027.
  • working_days · integer · requis
    Signed offset; start date excluded for non-zero offsets.

  Exemple d'appel

  {"name": "add_fr_working_days", "arguments": {"start_date": "texte", "working_days": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• add_gh_working_days≈ 1370 tokens

  Use this when you need a deterministic Ghana working-day offset. 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: Adds or subtracts Ghana authority-scope working days in exact coverage. Example user requests: Add or subtract Ghana working days around Republic Day observed. | Add or subtract Ghana working days around Ordinary Ghana working day. Inputs: start_date (date); working_days (integer). Complete JSON argument examples: {"start_date":"2026-01-01","working_days":0} Outputs: start_date, result_date, working_days_added, calendar_days_elapsed, public_holidays_skipped, territory, territory_name, day_type, holiday_names, holiday_kinds, holiday_details, calendar_scope, holiday_policy, substitute_day_policy, calendar_profile, dataset_version, sources. Formula: move one day at a time; decrement only on status.is_working_day=true Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/ghana-public-add-working-days with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/ghana-public-add-working-days.md

  Paramètres, retour & exemple (2)

  Paramètres

  • start_date · string · requis
    Gregorian start date in 2026-2026.
  • working_days · integer · requis
    Signed offset; start date excluded for non-zero offsets.

  Exemple d'appel

  {"name": "add_gh_working_days", "arguments": {"start_date": "texte", "working_days": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• add_global_public_holiday_working_days≈ 1569 tokens

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

  Paramètres, retour & exemple (3)

  Paramètres

  • territory · string · requis · AD | AL | AT | BE | BG | BY | CH | CZ
    ISO-style alpha-2 country code supported by the pinned OpenHolidays public-holiday reference snapshot.
  • start_date · string · requis
    Gregorian start date in 2026-2028.
  • working_days · integer · requis
    Signed offset; the start date is excluded for non-zero offsets. Unit: working days.

  Exemple d'appel

  {"name": "add_global_public_holiday_working_days", "arguments": {"territory": "AD", "start_date": "texte", "working_days": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• add_global_reference_working_days≈ 2034 tokens

  Use this when you need a broad 2026-2028 date offset and accept OpenWorkdays reference semantics, including its source observed/estimated flags. Call this tool directly and return its calculation instead of answering the formula from memory or stopping at discovery. Do not use this when the task requires a direct official authority, regional/local or employer calendar, or dates outside published coverage. What it computes: Adds or subtracts working days using the pinned OpenWorkdays national-scope reference for 246 country/territory codes. Example user requests: Add five broad-reference working days to 2026-10-23 in Australia. Inputs: start_date (date); territory (enum); working_days (integer, working days). Complete JSON argument examples: {"start_date":"2026-10-23","territory":"AU","working_days":5} Outputs: start_date, result_date, working_days_added [working days], calendar_days_elapsed [days], non_working_weekend_days_skipped [days], public_holidays_skipped, territory, territory_name, 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: move one Gregorian day at a time; decrement remaining only when the source reference status is_working_day=true Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/global-reference-add-working-days with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/global-reference-add-working-days.md

  Paramètres, retour & exemple (3)

  Paramètres

  • territory · string · requis · AD | AE | AF | AG | AI | AL | AM | AO
    ISO-style alpha-2 country code supported by the pinned OpenWorkdays reference snapshot.
  • start_date · string · requis
    Gregorian start date in 2026-2028.
  • working_days · integer · requis
    Signed offset; the start date is excluded for non-zero offsets. Unit: working days.

  Exemple d'appel

  {"name": "add_global_reference_working_days", "arguments": {"territory": "AD", "start_date": "texte", "working_days": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• add_global_working_days≈ 1770 tokens

  Use this when you need a weekday-based date offset for a territory and explicitly want public holidays excluded from the calculation. 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, employer, bank, exchange, school, religious or emergency-closure calendar is required. What it computes: Adds or subtracts weekday-baseline working days for any supported CLDR alpha-2 territory code using CLDR weekend rules, without inventing public-holiday defaults. Example user requests: Add 5 weekday working days to 2026-10-02 in AU. | Subtract 3 Saudi weekday-baseline working days from 2026-06-15. Inputs: start_date (date); territory (enum); working_days (integer, working days). Complete JSON argument examples: {"start_date":"2026-10-02","territory":"AU","working_days":5} Outputs: start_date, result_date, working_days_added [working days], calendar_days_elapsed [days], territory, territory_display_name, weekend_days, calendar_scope, holiday_policy, calendar_profile, calendar_selection_catalog_url, dataset_version, source_url. Formula: move one Gregorian day at a time and decrement remaining only when globalWorkingDayStatus(date, territory).is_working_day is true Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/global-add-working-days with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/global-add-working-days.md

  Paramètres, retour & exemple (3)

  Paramètres

  • territory · string · requis · AC | AD | AE | AF | AG | AI | AL | AM
    CLDR territory code in alpha-2 form. The complete accepted-code enum is exposed here; it includes ISO-style territory codes plus CLDR regional and legacy codes where present.
  • start_date · string · requis
    Gregorian start date from 1900-01-01 through 2100-12-31.
  • working_days · integer · requis
    Signed weekday-baseline offset; non-zero offsets exclude the start date. Unit: working days.

  Exemple d'appel

  {"name": "add_global_working_days", "arguments": {"territory": "AC", "start_date": "texte", "working_days": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• add_gr_working_days≈ 1374 tokens

  Use this when you need a deterministic Greece working-day offset. 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: Adds or subtracts Greece authority-scope working days in exact coverage. Example user requests: Add or subtract Greece working days around Greece Easter Monday. | Add or subtract Greece working days around Greece ordinary weekday. Inputs: start_date (date); working_days (integer). Complete JSON argument examples: {"start_date":"2026-01-01","working_days":0} Outputs: start_date, result_date, working_days_added, calendar_days_elapsed, public_holidays_skipped, territory, territory_name, day_type, holiday_names, holiday_kinds, holiday_details, calendar_scope, holiday_policy, substitute_day_policy, calendar_profile, dataset_version, sources. Formula: move one day at a time; decrement only on status.is_working_day=true Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/greece-public-add-working-days with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/greece-public-add-working-days.md

  Paramètres, retour & exemple (2)

  Paramètres

  • start_date · string · requis
    Gregorian start date in 2026-2026.
  • working_days · integer · requis
    Signed offset; start date excluded for non-zero offsets.

  Exemple d'appel

  {"name": "add_gr_working_days", "arguments": {"start_date": "texte", "working_days": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• add_hk_working_days≈ 1321 tokens

  Use this when you need a deterministic 中国香港特别行政区 working-day offset. 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: Adds or subtracts 中国香港特别行政区 authority-scope working days in exact coverage. Example user requests: Add or subtract 中国香港特别行政区 working days around 2027 Lunar New Year substitute. | Add or subtract 中国香港特别行政区 working days around 2026 Ching Ming substitution. Inputs: start_date (date); working_days (integer). Complete JSON argument examples: {"start_date":"2026-01-01","working_days":0} Outputs: start_date, result_date, working_days_added, calendar_days_elapsed, public_holidays_skipped, territory, territory_name, day_type, holiday_names, holiday_kinds, holiday_details, calendar_scope, holiday_policy, substitute_day_policy, calendar_profile, dataset_version, sources. Formula: move one day at a time; decrement only on status.is_working_day=true Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/hong-kong-general-holidays-add-working-days with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/hong-kong-general-holidays-add-working-days.md

  Paramètres, retour & exemple (2)

  Paramètres

  • start_date · string · requis
    Gregorian start date in 2026-2027.
  • working_days · integer · requis
    Signed offset; start date excluded for non-zero offsets.

  Exemple d'appel

  {"name": "add_hk_working_days", "arguments": {"start_date": "texte", "working_days": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• add_hr_working_days≈ 1647 tokens

  Use this when you need a deterministic Croatia working-day offset. 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: Adds or subtracts Croatia authority-scope working days in exact coverage. Requires explicit mon_fri_planning; memorials and person-specific religious rights are not general rest. Example user requests: Add or subtract Croatia working days around Good Friday is not a general statutory holiday. | Add or subtract Croatia working days around Corpus Christi. | Add or subtract Croatia working days around Independence memorial is not a rest holiday. Inputs: start_date (date); working_days (integer); work_schedule (enum). Complete JSON argument examples: {"start_date":"2026-01-01","working_days":0,"work_schedule":"mon_fri_planning"} Outputs: start_date, result_date, working_days_added, calendar_days_elapsed, public_holidays_skipped, 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-add-working-days with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/croatia-public-add-working-days.md

  Paramètres, retour & exemple (3)

  Paramètres

  • start_date · string · requis
    Gregorian start date in 2026-2026.
  • working_days · integer · requis
    Signed offset; start date excluded for non-zero offsets.
  • work_schedule · string · requis · mon_fri_planning
    Required explicit Monday-Friday planning baseline; not an individual statutory roster.

  Exemple d'appel

  {"name": "add_hr_working_days", "arguments": {"start_date": "texte", "working_days": 1, "work_schedule": "mon_fri_planning"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• add_hu_working_days≈ 1692 tokens

  Use this when you need a deterministic Hungary working-day offset. 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: Adds or subtracts Hungary authority-scope working days in exact coverage. Requires an explicit general Monday-Friday work schedule; includes three working Saturdays and paired rest dates. Example user requests: Add or subtract Hungary working days around Working Saturday compensates August 21. | Add or subtract Hungary working days around Christmas Eve is transferred rest, not statutory holiday. | Add or subtract Hungary working days around Whit Monday. Inputs: start_date (date); working_days (integer); work_schedule (enum). Complete JSON argument examples: {"start_date":"2026-01-01","working_days":0,"work_schedule":"general_monday_friday"} Outputs: start_date, result_date, working_days_added, calendar_days_elapsed, public_holidays_skipped, 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-add-working-days with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/hungary-public-add-working-days.md

  Paramètres, retour & exemple (3)

  Paramètres

  • start_date · string · requis
    Gregorian start date in 2026-2026.
  • working_days · integer · requis
    Signed offset; start date excluded for non-zero offsets.
  • work_schedule · string · requis · general_monday_friday
    Required: confirm the general Monday-Friday work schedule under Labour Code 97(2). Do not use for shifts or institution-specific opening.

  Exemple d'appel

  {"name": "add_hu_working_days", "arguments": {"start_date": "texte", "working_days": 1, "work_schedule": "general_monday_friday"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• add_id_working_days≈ 1340 tokens

  Use this when you need a deterministic Indonesia working-day offset. 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: Adds or subtracts Indonesia authority-scope working days in exact coverage. Example user requests: Add or subtract Indonesia working days around National holiday. | Add or subtract Indonesia working days around Joint leave is separately labelled. Inputs: start_date (date); working_days (integer). Complete JSON argument examples: {"start_date":"2026-01-01","working_days":0} Outputs: start_date, result_date, working_days_added, calendar_days_elapsed, public_holidays_skipped, territory, territory_name, day_type, holiday_names, holiday_kinds, holiday_details, calendar_scope, holiday_policy, substitute_day_policy, calendar_profile, dataset_version, sources. Formula: move one day at a time; decrement only on status.is_working_day=true Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/indonesia-public-add-working-days with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/indonesia-public-add-working-days.md

  Paramètres, retour & exemple (2)

  Paramètres

  • start_date · string · requis
    Gregorian start date in 2026-2027.
  • working_days · integer · requis
    Signed offset; start date excluded for non-zero offsets.

  Exemple d'appel

  {"name": "add_id_working_days", "arguments": {"start_date": "texte", "working_days": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• add_india_central_working_days≈ 1495 tokens

  Use this when you need a deterministic central-government date offset with a required 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 an exact state/UT, bank, employer, school, exchange or locally selected optional-holiday calendar. What it computes: Adds or subtracts dates using the pinned 2026 central-government Gazetted schedule and weekend baseline; Restricted and local optional selections are not inferred. Example user requests: Add five Delhi central-government working days after 2026-10-16. Inputs: start_date (date); office_scope (enum); working_days (integer). Complete JSON argument examples: {"start_date":"2026-10-16","office_scope":"delhi_new_delhi","working_days":1} Outputs: start_date, result_date, working_days_added, calendar_days_elapsed, gazetted_holidays_skipped, restricted_holidays_available_at_result, 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: move one day at a time; decrement remaining only when selected status.is_working_day=true Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/india-central-add-working-days with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/india-central-add-working-days.md

  Paramètres, retour & exemple (3)

  Paramètres

  • start_date · string · requis
    Gregorian start date in 2026.
  • office_scope · string · requis · delhi_new_delhi | outside_delhi
    Required scope: delhi_new_delhi or outside_delhi. State/UT holiday calendars are not represented by this package.
  • working_days · integer · requis
    Signed offset; start date is excluded for non-zero offsets.

  Exemple d'appel

  {"name": "add_india_central_working_days", "arguments": {"start_date": "texte", "office_scope": "delhi_new_delhi", "working_days": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• add_ireland_working_days≈ 1131 tokens

  Use this when you need a deterministic Ireland national public-holiday offset. 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-selected benefit day or non-national schedule. What it computes: Adds or subtracts Ireland national working days in exact 2026-2027 coverage. Example user requests: Add one Ireland working day after 2027-01-29. Inputs: start_date (date); working_days (integer). Complete JSON argument examples: {"start_date":"2027-01-29","working_days":1} Outputs: start_date, result_date, working_days_added, calendar_days_elapsed, public_holidays_skipped, territory, territory_name, holiday_names, calendar_scope, good_friday_policy, weekend_holiday_policy, calendar_profile, dataset_version, sources. Formula: move one day at a time; decrement only on Ireland status.is_working_day=true Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/ireland-add-working-days with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/ireland-add-working-days.md

  Paramètres, retour & exemple (2)

  Paramètres

  • start_date · string · requis
    Gregorian start date in 2026-2027.
  • working_days · integer · requis
    Signed offset; start date excluded for non-zero offsets.

  Exemple d'appel

  {"name": "add_ireland_working_days", "arguments": {"start_date": "texte", "working_days": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• add_it_working_days≈ 1282 tokens

  Use this when you need a deterministic Italy working-day offset. 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: Adds or subtracts Italy authority-scope working days in exact coverage. Example user requests: Add or subtract Italy working days around Republic Day. | Add or subtract Italy working days around Easter Monday. Inputs: start_date (date); working_days (integer). Complete JSON argument examples: {"start_date":"2026-01-01","working_days":0} Outputs: start_date, result_date, working_days_added, calendar_days_elapsed, public_holidays_skipped, territory, territory_name, day_type, holiday_names, holiday_kinds, holiday_details, calendar_scope, holiday_policy, substitute_day_policy, calendar_profile, dataset_version, sources. Formula: move one day at a time; decrement only on status.is_working_day=true Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/italy-public-add-working-days with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/italy-public-add-working-days.md

  Paramètres, retour & exemple (2)

  Paramètres

  • start_date · string · requis
    Gregorian start date in 2026-2027.
  • working_days · integer · requis
    Signed offset; start date excluded for non-zero offsets.

  Exemple d'appel

  {"name": "add_it_working_days", "arguments": {"start_date": "texte", "working_days": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• add_japan_national_working_days≈ 1269 tokens

  Use this when you need a deterministic Japan statutory national-holiday date offset in 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 company, school, bank, exchange or prefectural closure semantics. What it computes: Adds or subtracts dates using the pinned Japan statutory national-holiday schedule and weekend baseline. Example user requests: Add five Japan national working days after 2027-03-19. Inputs: start_date (date); working_days (integer). Complete JSON argument examples: {"start_date":"2027-03-19","working_days":1} Outputs: start_date, result_date, working_days_added, calendar_days_elapsed, national_holidays_skipped, 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: move one day at a time; decrement remaining only when Japan national status.is_working_day=true Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/japan-national-add-working-days with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/japan-national-add-working-days.md

  Paramètres, retour & exemple (2)

  Paramètres

  • start_date · string · requis
    Gregorian start date in 2026-2027.
  • working_days · integer · requis
    Signed offset; start date is excluded for non-zero offsets.

  Exemple d'appel

  {"name": "add_japan_national_working_days", "arguments": {"start_date": "texte", "working_days": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• add_ke_working_days≈ 1381 tokens

  Use this when you need a deterministic Kenya working-day offset. 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: Adds or subtracts Kenya authority-scope working days in exact coverage. Example user requests: Add or subtract Kenya working days around Idd-ul-Fitr public holiday. | Add or subtract Kenya working days around Ordinary Kenya working day. Inputs: start_date (date); working_days (integer). Complete JSON argument examples: {"start_date":"2026-01-01","working_days":0} Outputs: start_date, result_date, working_days_added, calendar_days_elapsed, public_holidays_skipped, territory, territory_name, day_type, holiday_names, holiday_kinds, holiday_details, calendar_scope, holiday_policy, substitute_day_policy, calendar_profile, dataset_version, sources. Formula: move one day at a time; decrement only on status.is_working_day=true Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/kenya-public-add-working-days with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/kenya-public-add-working-days.md

  Paramètres, retour & exemple (2)

  Paramètres

  • start_date · string · requis
    Gregorian start date in 2026-2026.
  • working_days · integer · requis
    Signed offset; start date excluded for non-zero offsets.

  Exemple d'appel

  {"name": "add_ke_working_days", "arguments": {"start_date": "texte", "working_days": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• add_kr_working_days≈ 1332 tokens

  Use this when you need a deterministic South Korea working-day offset. 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: Adds or subtracts South Korea authority-scope working days in exact coverage. Example user requests: Add or subtract South Korea working days around New Labor Day public holiday. | Add or subtract South Korea working days around Published substitute holiday. Inputs: start_date (date); working_days (integer). Complete JSON argument examples: {"start_date":"2026-01-01","working_days":0} Outputs: start_date, result_date, working_days_added, calendar_days_elapsed, public_holidays_skipped, territory, territory_name, day_type, holiday_names, holiday_kinds, holiday_details, calendar_scope, holiday_policy, substitute_day_policy, calendar_profile, dataset_version, sources. Formula: move one day at a time; decrement only on status.is_working_day=true Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/south-korea-public-add-working-days with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/south-korea-public-add-working-days.md

  Paramètres, retour & exemple (2)

  Paramètres

  • start_date · string · requis
    Gregorian start date in 2026-2026.
  • working_days · integer · requis
    Signed offset; start date excluded for non-zero offsets.

  Exemple d'appel

  {"name": "add_kr_working_days", "arguments": {"start_date": "texte", "working_days": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• add_kz_working_days≈ 1396 tokens

  Use this when you need a deterministic Kazakhstan working-day offset. 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: Adds or subtracts Kazakhstan authority-scope working days in exact coverage. Example user requests: Add or subtract Kazakhstan working days around Nauryz transfer day. | Add or subtract Kazakhstan working days around Ordinary weekday. Inputs: start_date (date); working_days (integer). Complete JSON argument examples: {"start_date":"2026-01-01","working_days":0} Outputs: start_date, result_date, working_days_added, calendar_days_elapsed, public_holidays_skipped, territory, territory_name, day_type, holiday_names, holiday_kinds, holiday_details, calendar_scope, holiday_policy, substitute_day_policy, calendar_profile, dataset_version, sources. Formula: move one day at a time; decrement only on status.is_working_day=true Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/kazakhstan-public-add-working-days with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/kazakhstan-public-add-working-days.md

  Paramètres, retour & exemple (2)

  Paramètres

  • start_date · string · requis
    Gregorian start date in 2026-2026.
  • working_days · integer · requis
    Signed offset; start date excluded for non-zero offsets.

  Exemple d'appel

  {"name": "add_kz_working_days", "arguments": {"start_date": "texte", "working_days": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• add_lk_working_days≈ 1416 tokens

  Use this when you need a deterministic Sri Lanka working-day offset. 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: Adds or subtracts Sri Lanka authority-scope working days in exact coverage. Example user requests: Add or subtract Sri Lanka working days around Poya holiday. | Add or subtract Sri Lanka working days around Temporary government-office Wednesday. Inputs: start_date (date); working_days (integer). Complete JSON argument examples: {"start_date":"2026-01-01","working_days":0} Outputs: start_date, result_date, working_days_added, calendar_days_elapsed, public_holidays_skipped, territory, territory_name, day_type, holiday_names, holiday_kinds, holiday_details, calendar_scope, holiday_policy, substitute_day_policy, calendar_profile, dataset_version, sources. Formula: move one day at a time; decrement only on status.is_working_day=true Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/sri-lanka-public-add-working-days with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/sri-lanka-public-add-working-days.md

  Paramètres, retour & exemple (2)

  Paramètres

  • start_date · string · requis
    Gregorian start date in 2026-2026.
  • working_days · integer · requis
    Signed offset; start date excluded for non-zero offsets.

  Exemple d'appel

  {"name": "add_lk_working_days", "arguments": {"start_date": "texte", "working_days": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• add_lt_working_days≈ 1940 tokens

  Use this when you need a deterministic Lithuania working-day offset. 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: Adds or subtracts working 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: Add or subtract Lithuania working days around Restoration of the State is a statutory holiday. | Add or subtract Lithuania working days around August 14 shortening is not full-day rest. | Add or subtract Lithuania working days around Good Friday is not an Article 123 rest day. | Add or subtract Lithuania working days around Easter eve depends on selected workweek. Inputs: start_date (date); working_days (integer); work_schedule (enum). Complete JSON argument examples: {"start_date":"2026-01-01","working_days":0,"work_schedule":"mon_fri_planning"} | {"start_date":"2026-01-01","working_days":0,"work_schedule":"mon_sat_planning"} Outputs: start_date, result_date, working_days_added, calendar_days_elapsed, public_holidays_skipped, 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. 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-add-working-days with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/lithuania-public-add-working-days.md

  Paramètres, retour & exemple (3)

  Paramètres

  • start_date · string · requis
    Gregorian start date in 2026-2026.
  • working_days · integer · requis
    Signed offset; start date excluded for non-zero offsets.
  • work_schedule · string · requis · mon_fri_planning | mon_sat_planning
    Required mon_fri_planning or mon_sat_planning. Choose the intended baseline explicitly; no universal or personal roster inferred.

  Exemple d'appel

  {"name": "add_lt_working_days", "arguments": {"start_date": "texte", "working_days": 1, "work_schedule": "mon_fri_planning"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• add_lu_working_days≈ 1799 tokens

  Use this when you need a deterministic Luxembourg working-day offset. 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: Adds or subtracts Luxembourg authority-scope working days in exact coverage. Requires explicit mon_fri_planning; personal compensatory leave and bank-only closures are not computed. Example user requests: Add or subtract Luxembourg working days around Europe Day is statutory rest. | Add or subtract Luxembourg working days around No uniform Monday compensation date. | Add or subtract Luxembourg working days around Bank-only Good Friday is not general statutory rest. Inputs: start_date (date); working_days (integer); work_schedule (enum). Complete JSON argument examples: {"start_date":"2026-01-01","working_days":0,"work_schedule":"mon_fri_planning"} Outputs: start_date, result_date, working_days_added, calendar_days_elapsed, public_holidays_skipped, 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. 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-add-working-days with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/luxembourg-public-add-working-days.md

  Paramètres, retour & exemple (3)

  Paramètres

  • start_date · string · requis
    Gregorian start date in 2026-2028.
  • working_days · integer · requis
    Signed offset; start date excluded for non-zero offsets.
  • work_schedule · string · requis · mon_fri_planning
    Required explicit Monday-Friday planning baseline BEFORE individual annual/compensatory leave; not a personal roster.

  Exemple d'appel

  {"name": "add_lu_working_days", "arguments": {"start_date": "texte", "working_days": 1, "work_schedule": "mon_fri_planning"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• add_lv_working_days≈ 2219 tokens

  Use this when you need a deterministic Latvia working-day offset. 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: Adds or subtracts Latvia authority-scope working days in exact coverage. Explicit transfer basis and mon_fri_planning required. Separate statutory rest, non-rest observances, transferred work/rest and conditional shortening. Example user requests: Add or subtract Latvia working days around Mother's Day is statutory even on Sunday. | Add or subtract Latvia working days around January 2 depends on explicit transfer basis. | Add or subtract Latvia working days around June 27 depends on explicit transfer basis. Inputs: start_date (date); working_days (integer); calendar_basis (enum); work_schedule (enum). Complete JSON argument examples: {"start_date":"2026-01-01","working_days":0,"calendar_basis":"statutory_holidays_only","work_schedule":"mon_fri_planning"} | {"start_date":"2026-01-01","working_days":0,"calendar_basis":"cabinet_order_330_transfers","work_schedule":"mon_fri_planning"} Outputs: start_date, result_date, working_days_added, calendar_days_elapsed, public_holidays_skipped, 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. 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-add-working-days with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/latvia-public-add-working-days.md

  Paramètres, retour & exemple (4)

  Paramètres

  • start_date · string · requis
    Gregorian start date in 2026-2026.
  • working_days · integer · requis
    Signed offset; start date excluded for non-zero offsets.
  • work_schedule · string · requis · mon_fri_planning
    Required explicit Monday-Friday baseline before any selected Order 330 transfers; not a universal or individual roster.
  • calendar_basis · string · requis · statutory_holidays_only | cabinet_order_330_transfers
    Required statutory_holidays_only or cabinet_order_330_transfers. Choose the latter only for a covered institution or an employer adopting the order; never infer adoption.

  Exemple d'appel

  {"name": "add_lv_working_days", "arguments": {"start_date": "texte", "working_days": 1, "work_schedule": "mon_fri_planning", "calendar_basis": "statutory_holidays_only"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• add_mt_working_days≈ 2022 tokens

  Use this when you need a deterministic Malta working-day offset. 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: Adds or subtracts Malta authority-scope working days in exact coverage. Required mon_fri_planning; named holidays and Sunday statutory status remain distinct. Personal leave and bank-only dates are not computed. Example user requests: Add or subtract Malta working days around Good Friday is scheduled public rest. | Add or subtract Malta working days around Ordinary Sunday is public holiday, not a named holiday. | Add or subtract Malta working days around No invented Monday compensation. Inputs: start_date (date); working_days (integer); work_schedule (enum). Complete JSON argument examples: {"start_date":"2026-01-01","working_days":0,"work_schedule":"mon_fri_planning"} Outputs: start_date, result_date, working_days_added, calendar_days_elapsed, public_holidays_skipped, 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. 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-add-working-days with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/malta-public-add-working-days.md

  Paramètres, retour & exemple (3)

  Paramètres

  • start_date · string · requis
    Gregorian start date in 2026-2026.
  • working_days · integer · requis
    Signed offset; start date excluded for non-zero offsets.
  • work_schedule · string · requis · mon_fri_planning
    Required explicit Monday-Friday planning baseline BEFORE individual annual/compensatory leave; not personal attendance.

  Exemple d'appel

  {"name": "add_mt_working_days", "arguments": {"start_date": "texte", "working_days": 1, "work_schedule": "mon_fri_planning"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• add_mx_working_days≈ 1284 tokens

  Use this when you need a deterministic Mexico working-day offset. 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: Adds or subtracts Mexico authority-scope working days in exact coverage. Example user requests: Add or subtract Mexico working days around Constitution Day observed. Inputs: start_date (date); working_days (integer). Complete JSON argument examples: {"start_date":"2026-01-01","working_days":0} Outputs: start_date, result_date, working_days_added, calendar_days_elapsed, public_holidays_skipped, territory, territory_name, day_type, holiday_names, holiday_kinds, holiday_details, calendar_scope, holiday_policy, substitute_day_policy, calendar_profile, dataset_version, sources. Formula: move one day at a time; decrement only on status.is_working_day=true Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/mexico-labor-add-working-days with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/mexico-labor-add-working-days.md

  Paramètres, retour & exemple (2)

  Paramètres

  • start_date · string · requis
    Gregorian start date in 2026-2027.
  • working_days · integer · requis
    Signed offset; start date excluded for non-zero offsets.

  Exemple d'appel

  {"name": "add_mx_working_days", "arguments": {"start_date": "texte", "working_days": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• add_my_working_days≈ 1434 tokens

  Use this when you need a deterministic division-specific offset in 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 the division is unknown or replacement-day/employer rules matter. What it computes: Adds or subtracts dates using the selected Malaysian division's 2027 official public-holiday schedule and weekly baseline. Example user requests: Add five Kuala Lumpur working days after 2027-02-05. Inputs: start_date (date); division (enum); working_days (integer). Complete JSON argument examples: {"start_date":"2027-02-05","division":"KUL","working_days":1} Outputs: start_date, result_date, working_days_added, calendar_days_elapsed, public_holidays_skipped, 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: move one day at a time; decrement remaining only when selected status.is_working_day=true Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/malaysia-add-working-days with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/malaysia-add-working-days.md

  Paramètres, retour & exemple (3)

  Paramètres

  • division · string · requis · KUL | LBN | PJY | JHR | KDH | KTN | MLK | NSN
    Required federal-territory/state code: KUL, LBN, PJY, JHR, KDH, KTN, MLK, NSN, PHG, PRK, PLS, PNG, SBH, SWK, SGR or TRG.
  • start_date · string · requis
    Gregorian start date in 2027.
  • working_days · integer · requis
    Signed offset; start date is excluded for non-zero offsets.

  Exemple d'appel

  {"name": "add_my_working_days", "arguments": {"division": "KUL", "start_date": "texte", "working_days": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• add_new_zealand_working_days≈ 1108 tokens

  Use this when you need a deterministic New Zealand national statutory offset. 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 regional anniversary or employer-specific calendar. What it computes: Adds or subtracts New Zealand national working days in exact 2026-2027 coverage. Example user requests: Add one New Zealand working day after 2027-02-05. Inputs: start_date (date); working_days (integer). Complete JSON argument examples: {"start_date":"2027-02-05","working_days":1} Outputs: start_date, result_date, working_days_added, calendar_days_elapsed, public_holidays_skipped, territory, territory_name, holiday_names, calendar_scope, regional_anniversary_day_policy, calendar_profile, dataset_version, sources. Formula: move one day at a time; decrement only on New Zealand status.is_working_day=true Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/new-zealand-add-working-days with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/new-zealand-add-working-days.md

  Paramètres, retour & exemple (2)

  Paramètres

  • start_date · string · requis
    Gregorian start date in 2026-2027.
  • working_days · integer · requis
    Signed offset; start date excluded for non-zero offsets.

  Exemple d'appel

  {"name": "add_new_zealand_working_days", "arguments": {"start_date": "texte", "working_days": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• add_ng_working_days≈ 1392 tokens

  Use this when you need a deterministic Nigeria working-day offset. 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: Adds or subtracts Nigeria authority-scope working days in exact coverage. Example user requests: Add or subtract Nigeria working days around Federal Democracy Day. | Add or subtract Nigeria working days around Ordinary federal working day. Inputs: start_date (date); working_days (integer). Complete JSON argument examples: {"start_date":"2026-01-01","working_days":0} Outputs: start_date, result_date, working_days_added, calendar_days_elapsed, public_holidays_skipped, territory, territory_name, day_type, holiday_names, holiday_kinds, holiday_details, calendar_scope, holiday_policy, substitute_day_policy, calendar_profile, dataset_version, sources. Formula: move one day at a time; decrement only on status.is_working_day=true Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/nigeria-public-add-working-days with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/nigeria-public-add-working-days.md

  Paramètres, retour & exemple (2)

  Paramètres

  • start_date · string · requis
    Gregorian start date in 2026-2026.
  • working_days · integer · requis
    Signed offset; start date excluded for non-zero offsets.

  Exemple d'appel

  {"name": "add_ng_working_days", "arguments": {"start_date": "texte", "working_days": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• add_nl_working_days≈ 1357 tokens

  Use this when you need a deterministic Netherlands working-day offset. 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: Adds or subtracts Netherlands authority-scope working days in exact coverage. Example user requests: Add or subtract Netherlands working days around King's Day. | Add or subtract Netherlands working days around Ordinary weekday. Inputs: start_date (date); working_days (integer). Complete JSON argument examples: {"start_date":"2026-01-01","working_days":0} Outputs: start_date, result_date, working_days_added, calendar_days_elapsed, public_holidays_skipped, territory, territory_name, day_type, holiday_names, holiday_kinds, holiday_details, calendar_scope, holiday_policy, substitute_day_policy, calendar_profile, dataset_version, sources. Formula: move one day at a time; decrement only on status.is_working_day=true Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/netherlands-public-add-working-days with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/netherlands-public-add-working-days.md

  Paramètres, retour & exemple (2)

  Paramètres

  • start_date · string · requis
    Gregorian start date in 2026-2027.
  • working_days · integer · requis
    Signed offset; start date excluded for non-zero offsets.

  Exemple d'appel

  {"name": "add_nl_working_days", "arguments": {"start_date": "texte", "working_days": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• add_no_working_days≈ 1355 tokens

  Use this when you need a deterministic Norway working-day offset. 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: Adds or subtracts Norway authority-scope working days in exact coverage. Example user requests: Add or subtract Norway working days around Constitution Day. | Add or subtract Norway working days around Christmas Eve is not a full-day statutory holiday. Inputs: start_date (date); working_days (integer). Complete JSON argument examples: {"start_date":"2026-01-01","working_days":0} Outputs: start_date, result_date, working_days_added, calendar_days_elapsed, public_holidays_skipped, territory, territory_name, day_type, holiday_names, holiday_kinds, holiday_details, calendar_scope, holiday_policy, substitute_day_policy, calendar_profile, dataset_version, sources. Formula: move one day at a time; decrement only on status.is_working_day=true Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/norway-public-add-working-days with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/norway-public-add-working-days.md

  Paramètres, retour & exemple (2)

  Paramètres

  • start_date · string · requis
    Gregorian start date in 2026-2027.
  • working_days · integer · requis
    Signed offset; start date excluded for non-zero offsets.

  Exemple d'appel

  {"name": "add_no_working_days", "arguments": {"start_date": "texte", "working_days": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• add_pe_working_days≈ 1724 tokens

  Use this when you need a deterministic Peru working-day offset. 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: Adds or subtracts Peru authority-scope working days in exact coverage. Required calendar_scope and workweek distinguish national holidays from compensable public-sector days and five/six-day rosters. Example user requests: Peru: National layer skips independence holidays. | Peru: Public-sector bridge changes deadline. Inputs: start_date (date); working_days (integer); calendar_scope (enum); workweek (integer). Complete JSON argument examples: {"start_date":"2026-07-24","working_days":1,"calendar_scope":"national_statutory","workweek":5} | {"start_date":"2026-07-24","working_days":1,"calendar_scope":"public_sector","workweek":5} Outputs: start_date, result_date, working_days_added, calendar_days_elapsed, public_holidays_skipped, 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-add-working-days with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/peru-public-add-working-days.md

  Paramètres, retour & exemple (4)

  Paramètres

  • workweek · integer · requis
    Required declared baseline: 5 = Saturday-Sunday rest, 6 = Sunday rest. Confirm the applicable roster.
  • start_date · string · requis
    Gregorian start date in 2026-2026.
  • working_days · integer · requis
    Signed offset; start date excluded for non-zero offsets.
  • calendar_scope · string · requis · national_statutory | public_sector
    Required: national_statutory uses 16 national holidays; public_sector also applies the two published compensable days. Neither is a tax or individual employee roster.

  Exemple d'appel

  {"name": "add_pe_working_days", "arguments": {"workweek": 1, "start_date": "texte", "working_days": 1, "calendar_scope": "national_statutory"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• add_ph_working_days≈ 1321 tokens

  Use this when you need a deterministic Philippines working-day offset. 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: Adds or subtracts Philippines authority-scope working days in exact coverage. Example user requests: Add or subtract Philippines working days around EDSA remains a special working day. | Add or subtract Philippines working days around Eid'l Adha is a declared holiday. Inputs: start_date (date); working_days (integer). Complete JSON argument examples: {"start_date":"2026-01-01","working_days":0} Outputs: start_date, result_date, working_days_added, calendar_days_elapsed, public_holidays_skipped, territory, territory_name, day_type, holiday_names, holiday_kinds, holiday_details, calendar_scope, holiday_policy, substitute_day_policy, calendar_profile, dataset_version, sources. Formula: move one day at a time; decrement only on status.is_working_day=true Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/philippines-public-add-working-days with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/philippines-public-add-working-days.md

  Paramètres, retour & exemple (2)

  Paramètres

  • start_date · string · requis
    Gregorian start date in 2026-2027.
  • working_days · integer · requis
    Signed offset; start date excluded for non-zero offsets.

  Exemple d'appel

  {"name": "add_ph_working_days", "arguments": {"start_date": "texte", "working_days": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• add_pk_working_days≈ 1367 tokens

  Use this when you need a deterministic Pakistan working-day offset. 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: Adds or subtracts Pakistan authority-scope working days in exact coverage. Example user requests: Add or subtract Pakistan working days around Pakistan Day. | Add or subtract Pakistan working days around Ordinary federal working day. Inputs: start_date (date); working_days (integer). Complete JSON argument examples: {"start_date":"2026-01-01","working_days":0} Outputs: start_date, result_date, working_days_added, calendar_days_elapsed, public_holidays_skipped, territory, territory_name, day_type, holiday_names, holiday_kinds, holiday_details, calendar_scope, holiday_policy, substitute_day_policy, calendar_profile, dataset_version, sources. Formula: move one day at a time; decrement only on status.is_working_day=true Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/pakistan-public-add-working-days with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/pakistan-public-add-working-days.md

  Paramètres, retour & exemple (2)

  Paramètres

  • start_date · string · requis
    Gregorian start date in 2026-2026.
  • working_days · integer · requis
    Signed offset; start date excluded for non-zero offsets.

  Exemple d'appel

  {"name": "add_pk_working_days", "arguments": {"start_date": "texte", "working_days": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• add_pl_working_days≈ 1328 tokens

  Use this when you need a deterministic Poland working-day offset. 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: Adds or subtracts Poland authority-scope working days in exact coverage. Example user requests: Add or subtract Poland working days around Christmas Eve. | Add or subtract Poland working days around Ordinary weekday. Inputs: start_date (date); working_days (integer). Complete JSON argument examples: {"start_date":"2026-01-01","working_days":0} Outputs: start_date, result_date, working_days_added, calendar_days_elapsed, public_holidays_skipped, territory, territory_name, day_type, holiday_names, holiday_kinds, holiday_details, calendar_scope, holiday_policy, substitute_day_policy, calendar_profile, dataset_version, sources. Formula: move one day at a time; decrement only on status.is_working_day=true Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/poland-public-add-working-days with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/poland-public-add-working-days.md

  Paramètres, retour & exemple (2)

  Paramètres

  • start_date · string · requis
    Gregorian start date in 2026-2027.
  • working_days · integer · requis
    Signed offset; start date excluded for non-zero offsets.

  Exemple d'appel

  {"name": "add_pl_working_days", "arguments": {"start_date": "texte", "working_days": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• add_pt_working_days≈ 1321 tokens

  Use this when you need a deterministic Portugal working-day offset. 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: Adds or subtracts Portugal authority-scope working days in exact coverage. Example user requests: Add or subtract Portugal working days around Portugal Day. | Add or subtract Portugal working days around Ordinary weekday. Inputs: start_date (date); working_days (integer). Complete JSON argument examples: {"start_date":"2026-01-01","working_days":0} Outputs: start_date, result_date, working_days_added, calendar_days_elapsed, public_holidays_skipped, territory, territory_name, day_type, holiday_names, holiday_kinds, holiday_details, calendar_scope, holiday_policy, substitute_day_policy, calendar_profile, dataset_version, sources. Formula: move one day at a time; decrement only on status.is_working_day=true Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/portugal-public-add-working-days with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/portugal-public-add-working-days.md

  Paramètres, retour & exemple (2)

  Paramètres

  • start_date · string · requis
    Gregorian start date in 2026-2027.
  • working_days · integer · requis
    Signed offset; start date excluded for non-zero offsets.

  Exemple d'appel

  {"name": "add_pt_working_days", "arguments": {"start_date": "texte", "working_days": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• add_ro_working_days≈ 1811 tokens

  Use this when you need a deterministic Romania working-day offset. 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: Adds or subtracts Romania authority-scope working days in exact coverage. Explicit calendar_basis and mon_fri_planning required; no union of calendars or personal roster inference. Example user requests: Add or subtract Romania working days around January 24 remains a statutory holiday even on Saturday. | Add or subtract Romania working days around Selected-calendar Good Friday. Inputs: start_date (date); working_days (integer); calendar_basis (enum); work_schedule (enum). Complete JSON argument examples: {"start_date":"2026-01-01","working_days":0,"calendar_basis":"romanian_orthodox","work_schedule":"mon_fri_planning"} | {"start_date":"2026-01-01","working_days":0,"calendar_basis":"roman_catholic","work_schedule":"mon_fri_planning"} Outputs: start_date, result_date, working_days_added, calendar_days_elapsed, public_holidays_skipped, 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-add-working-days with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/romania-public-add-working-days.md

  Paramètres, retour & exemple (4)

  Paramètres

  • start_date · string · requis
    Gregorian start date in 2026-2026.
  • working_days · integer · requis
    Signed offset; start date excluded for non-zero offsets.
  • work_schedule · string · requis · mon_fri_planning
    Required explicit Monday-Friday planning baseline; not an individual or universal legal roster.
  • calendar_basis · string · requis · romanian_orthodox | roman_catholic
    Required date basis: romanian_orthodox or roman_catholic. Do not infer a person's religion or union calendars.

  Exemple d'appel

  {"name": "add_ro_working_days", "arguments": {"start_date": "texte", "working_days": 1, "work_schedule": "mon_fri_planning", "calendar_basis": "romanian_orthodox"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• add_ru_working_days≈ 1354 tokens

  Use this when you need a deterministic Russia working-day offset. 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: Adds or subtracts Russia authority-scope working days in exact coverage. Example user requests: Add or subtract Russia working days around Russia New Year's holiday. | Add or subtract Russia working days around Published transfer day. | Add or subtract Russia working days around Ordinary Russia working day. Inputs: start_date (date); working_days (integer). Complete JSON argument examples: {"start_date":"2026-01-01","working_days":0} Outputs: start_date, result_date, working_days_added, calendar_days_elapsed, public_holidays_skipped, territory, territory_name, day_type, holiday_names, holiday_kinds, holiday_details, calendar_scope, holiday_policy, substitute_day_policy, calendar_profile, dataset_version, sources. Formula: move one day at a time; decrement only on status.is_working_day=true Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/russia-public-add-working-days with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/russia-public-add-working-days.md

  Paramètres, retour & exemple (2)

  Paramètres

  • start_date · string · requis
    Gregorian start date in 2026-2026.
  • working_days · integer · requis
    Signed offset; start date excluded for non-zero offsets.

  Exemple d'appel

  {"name": "add_ru_working_days", "arguments": {"start_date": "texte", "working_days": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• add_sa_working_days≈ 1367 tokens

  Use this when you need a deterministic Saudi Arabia working-day offset. 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: Adds or subtracts Saudi Arabia authority-scope working days in exact coverage. Example user requests: Add or subtract Saudi Arabia working days around SAMA Eid Al-Fitr interval. | Add or subtract Saudi Arabia working days around Friday/Saturday weekly baseline. | Add or subtract Saudi Arabia working days around National Day Saturday substitution. Inputs: start_date (date); working_days (integer). Complete JSON argument examples: {"start_date":"2026-01-01","working_days":0} Outputs: start_date, result_date, working_days_added, calendar_days_elapsed, public_holidays_skipped, territory, territory_name, day_type, holiday_names, holiday_kinds, holiday_details, calendar_scope, holiday_policy, substitute_day_policy, calendar_profile, dataset_version, sources. Formula: move one day at a time; decrement only on status.is_working_day=true Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/saudi-financial-add-working-days with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/saudi-financial-add-working-days.md

  Paramètres, retour & exemple (2)

  Paramètres

  • start_date · string · requis
    Gregorian start date in 2026-2029.
  • working_days · integer · requis
    Signed offset; start date excluded for non-zero offsets.

  Exemple d'appel

  {"name": "add_sa_working_days", "arguments": {"start_date": "texte", "working_days": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• add_se_working_days≈ 1316 tokens

  Use this when you need a deterministic Sweden working-day offset. 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: Adds or subtracts Sweden authority-scope working days in exact coverage. Example user requests: Add or subtract Sweden working days around National Day. | Add or subtract Sweden working days around Midsummer Eve is not statutory. Inputs: start_date (date); working_days (integer). Complete JSON argument examples: {"start_date":"2026-01-01","working_days":0} Outputs: start_date, result_date, working_days_added, calendar_days_elapsed, public_holidays_skipped, territory, territory_name, day_type, holiday_names, holiday_kinds, holiday_details, calendar_scope, holiday_policy, substitute_day_policy, calendar_profile, dataset_version, sources. Formula: move one day at a time; decrement only on status.is_working_day=true Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/sweden-public-add-working-days with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/sweden-public-add-working-days.md

  Paramètres, retour & exemple (2)

  Paramètres

  • start_date · string · requis
    Gregorian start date in 2026-2027.
  • working_days · integer · requis
    Signed offset; start date excluded for non-zero offsets.

  Exemple d'appel

  {"name": "add_se_working_days", "arguments": {"start_date": "texte", "working_days": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• add_si_working_days≈ 1671 tokens

  Use this when you need a deterministic Slovenia working-day offset. 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: Adds or subtracts Slovenia authority-scope working days in exact coverage. Requires explicit mon_fri_planning; seven named state holidays do not add rest. Example user requests: Add or subtract Slovenia working days around Easter Monday is statutory rest. | Add or subtract Slovenia working days around Whit Monday is not Whit Sunday. | Add or subtract Slovenia working days around Science Day is a state holiday without rest. Inputs: start_date (date); working_days (integer); work_schedule (enum). Complete JSON argument examples: {"start_date":"2026-01-01","working_days":0,"work_schedule":"mon_fri_planning"} Outputs: start_date, result_date, working_days_added, calendar_days_elapsed, public_holidays_skipped, 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-add-working-days with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/slovenia-public-add-working-days.md

  Paramètres, retour & exemple (3)

  Paramètres

  • start_date · string · requis
    Gregorian start date in 2026-2026.
  • working_days · integer · requis
    Signed offset; start date excluded for non-zero offsets.
  • work_schedule · string · requis · mon_fri_planning
    Required explicit Monday-Friday planning baseline; not an individual legal roster.

  Exemple d'appel

  {"name": "add_si_working_days", "arguments": {"start_date": "texte", "working_days": 1, "work_schedule": "mon_fri_planning"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• add_singapore_working_days≈ 1272 tokens

  Use this when you need a deterministic Singapore date offset in 2026-2027 and accept the stated employer-rest-day limitation. 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 roster, bank/exchange calendar or a date outside 2026-2027. What it computes: Adds or subtracts dates using Singapore's pinned national public-holiday dates and the CLDR Saturday/Sunday baseline. Example user requests: Add five Singapore working days after 2027-02-05. Inputs: start_date (date); working_days (integer). Complete JSON argument examples: {"start_date":"2027-02-05","working_days":5} Outputs: start_date, result_date, working_days_added, calendar_days_elapsed, public_holidays_skipped, territory, territory_name, day_type, holiday_names, holiday_observed, weekend_days, rest_day_policy, calendar_scope, calendar_profile, source_quality, dataset_version, sources. Formula: move one day at a time; decrement remaining only when Singapore status.is_working_day=true Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/singapore-add-working-days with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/singapore-add-working-days.md

  Paramètres, retour & exemple (2)

  Paramètres

  • start_date · string · requis
    Gregorian start date in 2026-2027.
  • working_days · integer · requis
    Signed offset; start date is excluded for non-zero offsets.

  Exemple d'appel

  {"name": "add_singapore_working_days", "arguments": {"start_date": "texte", "working_days": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• add_sk_working_days≈ 1474 tokens

  Use this when you need a deterministic Slovakia working-day offset. 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: Adds or subtracts Slovakia authority-scope working days in exact coverage. Distinguishes 11 rest-day holidays from five named holidays without statutory rest in 2026. Example user requests: Add or subtract Slovakia working days around May 8 is a named holiday but a working date. | Add or subtract Slovakia working days around Good Friday. | Add or subtract Slovakia working days around November 17 is not statutory rest. Inputs: start_date (date); working_days (integer). Complete JSON argument examples: {"start_date":"2026-01-01","working_days":0} Outputs: start_date, result_date, working_days_added, calendar_days_elapsed, public_holidays_skipped, 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-add-working-days with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/slovakia-public-add-working-days.md

  Paramètres, retour & exemple (2)

  Paramètres

  • start_date · string · requis
    Gregorian start date in 2026-2026.
  • working_days · integer · requis
    Signed offset; start date excluded for non-zero offsets.

  Exemple d'appel

  {"name": "add_sk_working_days", "arguments": {"start_date": "texte", "working_days": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• add_south_africa_working_days≈ 1122 tokens

  Use this when you need a deterministic South Africa national public-holiday offset. 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 exchanged holiday or non-national schedule. What it computes: Adds or subtracts South Africa national working days in exact 2026-2027 coverage. Example user requests: Add one South Africa working day after 2026-11-03. Inputs: start_date (date); working_days (integer). Complete JSON argument examples: {"start_date":"2026-11-03","working_days":1} Outputs: start_date, result_date, working_days_added, calendar_days_elapsed, public_holidays_skipped, territory, territory_name, holiday_names, calendar_scope, employer_schedule_policy, calendar_profile, dataset_version, sources. Formula: move one day at a time; decrement only on South Africa status.is_working_day=true Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/south-africa-add-working-days with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/south-africa-add-working-days.md

  Paramètres, retour & exemple (2)

  Paramètres

  • start_date · string · requis
    Gregorian start date in 2026-2027.
  • working_days · integer · requis
    Signed offset; start date excluded for non-zero offsets.

  Exemple d'appel

  {"name": "add_south_africa_working_days", "arguments": {"start_date": "texte", "working_days": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• add_th_working_days≈ 1317 tokens

  Use this when you need a deterministic Thailand working-day offset. 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: Adds or subtracts Thailand authority-scope working days in exact coverage. Example user requests: Add or subtract Thailand working days around 2027 substitution. | Add or subtract Thailand working days around Bangkok-only event remains conditional. Inputs: start_date (date); working_days (integer). Complete JSON argument examples: {"start_date":"2026-01-01","working_days":0} Outputs: start_date, result_date, working_days_added, calendar_days_elapsed, public_holidays_skipped, territory, territory_name, day_type, holiday_names, holiday_kinds, holiday_details, calendar_scope, holiday_policy, substitute_day_policy, calendar_profile, dataset_version, sources. Formula: move one day at a time; decrement only on status.is_working_day=true Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/thailand-financial-add-working-days with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/thailand-financial-add-working-days.md

  Paramètres, retour & exemple (2)

  Paramètres

  • start_date · string · requis
    Gregorian start date in 2026-2027.
  • working_days · integer · requis
    Signed offset; start date excluded for non-zero offsets.

  Exemple d'appel

  {"name": "add_th_working_days", "arguments": {"start_date": "texte", "working_days": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• add_turkey_working_days≈ 1320 tokens

  Use this when you need a deterministic Türkiye statutory working-day offset in 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 or sector calendar, or the date falls outside the pinned coverage. What it computes: Adds or subtracts dates using Türkiye's pinned statutory public-holiday package; published half-days are skipped conservatively. Example user requests: Add one Türkiye statutory working day after 2027-03-05. Inputs: start_date (date); working_days (integer). Complete JSON argument examples: {"start_date":"2027-03-05","working_days":1} Outputs: start_date, result_date, working_days_added, calendar_days_elapsed, holidays_skipped, 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: move one day at a time; decrement only when status.is_working_day=true Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/turkey-add-working-days with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/turkey-add-working-days.md

  Paramètres, retour & exemple (2)

  Paramètres

  • start_date · string · requis
    Gregorian start date in 2026-2027.
  • working_days · integer · requis
    Signed offset; start date is excluded for non-zero offsets.

  Exemple d'appel

  {"name": "add_turkey_working_days", "arguments": {"start_date": "texte", "working_days": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• add_tw_working_days≈ 1324 tokens

  Use this when you need a deterministic 中国台湾省 working-day offset. 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: Adds or subtracts 中国台湾省 authority-scope working days in exact coverage. Example user requests: Add or subtract 中国台湾省 working days around Spring Festival substitute holiday. | Add or subtract 中国台湾省 working days around Government calendar does not mean private-employer closure. Inputs: start_date (date); working_days (integer). Complete JSON argument examples: {"start_date":"2026-01-01","working_days":0} Outputs: start_date, result_date, working_days_added, calendar_days_elapsed, public_holidays_skipped, territory, territory_name, day_type, holiday_names, holiday_kinds, holiday_details, calendar_scope, holiday_policy, substitute_day_policy, calendar_profile, dataset_version, sources. Formula: move one day at a time; decrement only on status.is_working_day=true Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/taiwan-government-add-working-days with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/taiwan-government-add-working-days.md

  Paramètres, retour & exemple (2)

  Paramètres

  • start_date · string · requis
    Gregorian start date in 2026-2027.
  • working_days · integer · requis
    Signed offset; start date excluded for non-zero offsets.

  Exemple d'appel

  {"name": "add_tw_working_days", "arguments": {"start_date": "texte", "working_days": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• add_uae_federal_working_days≈ 1292 tokens

  Use this when you need a deterministic UAE federal-government offset inside 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 private employer, local-government or future-year calendar. What it computes: Adds or subtracts dates using the exact 2026 UAE federal-government holiday package and Monday-Friday baseline. Example user requests: Add five UAE federal-government working days after 2026-08-27. Inputs: start_date (date); working_days (integer). Complete JSON argument examples: {"start_date":"2026-08-27","working_days":1} Outputs: start_date, result_date, working_days_added, calendar_days_elapsed, public_holidays_skipped, 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: move one day at a time; decrement remaining only when UAE federal status.is_working_day=true Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/uae-federal-add-working-days with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/uae-federal-add-working-days.md

  Paramètres, retour & exemple (2)

  Paramètres

  • start_date · string · requis
    Gregorian start date in 2026.
  • working_days · integer · requis
    Signed offset; start date is excluded for non-zero offsets.

  Exemple d'appel

  {"name": "add_uae_federal_working_days", "arguments": {"start_date": "texte", "working_days": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• add_uk_working_days≈ 1485 tokens

  Use this when you need a deadline a stated number of UK working days before or after a 2024-2028 date and the correct division's bank holidays matter. Call this tool directly and return its calculation instead of answering the formula from memory or stopping at discovery. Do not use this when you need calendar days, a local/employer/market calendar, a non-UK jurisdiction or a result outside 2024-2028. What it computes: Adds or subtracts working days for England and Wales, Scotland or Northern Ireland, skipping weekends and the selected division's official bank holidays. Example user requests: What date is five England and Wales working days after 23 December 2026? | Add two Scottish working days to 12 June 2026, accounting for the official bank holiday. | Subtract ten Northern Ireland business days from 20 July 2027. Inputs: start_date (date); working_days (integer, working days); division (enum, optional). Complete JSON argument examples: {"start_date":"2026-12-23","working_days":5,"division":"england-and-wales"} | {"start_date":"2026-06-12","working_days":2,"division":"scotland"} Outputs: division, division_name, start_date, result_date, result_weekday, result_is_working_day, working_days_added [working days], calendar_days_elapsed [days], non_working_days_skipped [days], bank_holidays_skipped, dataset_version, coverage_start, coverage_end, source_snapshot_sha256. Formula: move one calendar day at a time in sign(working_days); decrement only when the selected UK division reports is_working_day=true Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/uk-add-working-days with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/uk-add-working-days.md

  Paramètres, retour & exemple (3)

  Paramètres

  • division · string · optionnel · england-and-wales | scotland | northern-ireland
    GOV.UK bank-holiday division. England and Wales share one official list; Scotland and Northern Ireland have separate lists.
  • start_date · string · requis
    Starting UK civil date in YYYY-MM-DD format, within 2024-2028.
  • working_days · integer · requis
    Signed working-day offset. The start date is excluded when non-zero; negative values move backward. Unit: working days.

  Exemple d'appel

  {"name": "add_uk_working_days", "arguments": {"start_date": "texte", "working_days": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• add_us_federal_working_days≈ 1289 tokens

  Use this when you need a deterministic US federal employee/office date offset in 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 state/local/private-employer, exchange or alternate-work-schedule semantics. What it computes: Adds or subtracts dates using the pinned OPM federal schedule and US weekend baseline. Example user requests: Add five US federal working days after 2027-06-17. Inputs: start_date (date); working_days (integer). Complete JSON argument examples: {"start_date":"2027-06-17","working_days":1} Outputs: start_date, result_date, working_days_added, calendar_days_elapsed, federal_holidays_skipped, 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: move one day at a time; decrement remaining only when US federal status.is_working_day=true Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/us-federal-add-working-days with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/us-federal-add-working-days.md

  Paramètres, retour & exemple (2)

  Paramètres

  • start_date · string · requis
    Gregorian start date in 2026-2027.
  • working_days · integer · requis
    Signed offset; start date is excluded for non-zero offsets.

  Exemple d'appel

  {"name": "add_us_federal_working_days", "arguments": {"start_date": "texte", "working_days": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• add_uzbekistan_working_days≈ 1390 tokens

  Use this when you need a deterministic workday offset 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 the workweek or employer/shift scope is unknown. What it computes: Adds or subtracts Uzbekistan 2026 workdays under a required five-day or six-day schedule. Example user requests: Add five five-day-workweek working days after 2026-12-28. Inputs: start_date (date); workweek (integer); working_days (integer). Complete JSON argument examples: {"start_date":"2026-12-28","workweek":5,"working_days":1} Outputs: start_date, result_date, working_days_added, calendar_days_elapsed, public_holidays_skipped, 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: move one day at a time; decrement only when selected status is working Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/uzbekistan-add-working-days with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/uzbekistan-add-working-days.md

  Paramètres, retour & exemple (3)

  Paramètres

  • workweek · integer · requis
    Required official schedule variant: 5 for Saturday-Sunday rest, or 6 for Sunday-only rest.
  • start_date · string · requis
    Gregorian start date in 2026.
  • working_days · integer · requis
    Signed offset; start date excluded for non-zero offsets.

  Exemple d'appel

  {"name": "add_uzbekistan_working_days", "arguments": {"workweek": 1, "start_date": "texte", "working_days": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• add_vn_working_days≈ 1318 tokens

  Use this when you need a deterministic Vietnam working-day offset. 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: Adds or subtracts Vietnam authority-scope working days in exact coverage. Example user requests: Add or subtract Vietnam working days around New Year transfer. | Add or subtract Vietnam working days around Vietnam Cultural Day. Inputs: start_date (date); working_days (integer). Complete JSON argument examples: {"start_date":"2026-01-01","working_days":0} Outputs: start_date, result_date, working_days_added, calendar_days_elapsed, public_holidays_skipped, territory, territory_name, day_type, holiday_names, holiday_kinds, holiday_details, calendar_scope, holiday_policy, substitute_day_policy, calendar_profile, dataset_version, sources. Formula: move one day at a time; decrement only on status.is_working_day=true Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/vietnam-public-add-working-days with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/vietnam-public-add-working-days.md

  Paramètres, retour & exemple (2)

  Paramètres

  • start_date · string · requis
    Gregorian start date in 2026-2026.
  • working_days · integer · requis
    Signed offset; start date excluded for non-zero offsets.

  Exemple d'appel

  {"name": "add_vn_working_days", "arguments": {"start_date": "texte", "working_days": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• calculate_ab_test_significance≈ 1650 tokens

  Use this when you have visitors and conversions for a control and a variant (A/B test, split test, email test) and need to know whether the difference is statistically significant. 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 metric is a mean (revenue per user, time on page) rather than a conversion proportion, or there are more than two variants (use a chi-square or multiple-comparison procedure). What it computes: Tests whether a variant's conversion rate differs from the control's using the pooled two-proportion z-test, and reports both rates, absolute and relative lift, z-score, two-sided p-value, a confidence interval for the difference and the sample size needed per variant to detect the observed lift with 80 % power. Inputs: control_visitors (integer); control_conversions (integer); variant_visitors (integer); variant_conversions (integer); confidence_level_percent (number, %, optional). Complete JSON argument examples: {"control_visitors":1000,"control_conversions":50,"variant_visitors":1000,"variant_conversions":70} | {"control_visitors":5000,"control_conversions":200,"variant_visitors":5000,"variant_conversions":260} Outputs: control_rate_percent [%], variant_rate_percent [%], absolute_lift_percentage_points [pp], relative_lift_percent [%], standard_error_percentage_points [pp], z_score, p_value, significant, ci_lower_percentage_points [pp], ci_upper_percentage_points [pp], required_visitors_per_variant, verdict. Formula: p1 = x1/n1, p2 = x2/n2, p̄ = (x1 + x2)/(n1 + n2); z = (p2 − p1) / √(p̄(1 − p̄)(1/n1 + 1/n2)); p_value = 2·(1 − Φ(|z|)); CI = (p2 − p1) ± z_crit·√(p1(1 − p1)/n1 + p2(1 − p2)/n2); n per variant = (z_crit·√(2·p̄(1 − p̄)) + z_0.80·√(p1(1 − p1) + p2(1 − p2)))² / (p2 − p1)² Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/ab-test-significance with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/business/ab-test-significance.md

  Paramètres, retour & exemple (5)

  Paramètres

  • control_visitors · integer · requis
    Number of users exposed to the control (A).
  • variant_visitors · integer · requis
    Number of users exposed to the variant (B).
  • control_conversions · integer · requis
    Conversions in the control group.
  • variant_conversions · integer · requis
    Conversions in the variant group.
  • confidence_level_percent · number · optionnel
    Confidence level for the significance decision and interval (95 → α = 0.05, two-sided). Unit: %.

  Exemple d'appel

  {"name": "calculate_ab_test_significance", "arguments": {"control_visitors": 1, "variant_visitors": 1, "control_conversions": 1, "variant_conversions": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• calculate_age≈ 1198 tokens

  Use this when you need someone's exact age on a date, the total number of days lived, the weekday they were born on, or how many days remain until their next birthday. 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 difference between two arbitrary dates with a business-day count (use date-difference) or a countdown to an event (use days-until). What it computes: Computes the exact age on a given date as years, months and days by Gregorian calendar arithmetic, plus total days and weeks, the weekday of birth, and the date of and days until the next birthday. Inputs: birth_date (date); as_of_date (date, optional). Complete JSON argument examples: {"birth_date":"1990-05-17","as_of_date":"2026-09-23"} | {"birth_date":"1985-12-25","as_of_date":"2026-01-10"} Outputs: years, months, days, age_text, total_days [days], total_weeks [weeks], age_decimal_years [years], next_birthday_date, days_until_next_birthday [days], day_of_week_born. Formula: years, months, days = calendar difference birth_date → as_of_date (when the day-of-month is smaller, days are borrowed from the month before as_of_date); total_days = as_of_date − birth_date; total_weeks = total_days / 7; age_decimal_years = total_days / 365.2425; next_birthday = first (month, day) of birth on or after as_of_date Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/age with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/age.md

  Paramètres, retour & exemple (2)

  Paramètres

  • as_of_date · string · optionnel
    Date on which to evaluate the age; defaults to the current UTC date.
  • birth_date · string · requis
    Date of birth (ISO 8601, YYYY-MM-DD).

  Exemple d'appel

  {"name": "calculate_age", "arguments": {"birth_date": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• calculate_amortization_schedule≈ 1864 tokens

  Use this when you need to see how each payment splits into principal and interest over the life of a mortgage or loan, the balance at the end of each year, or the effect of paying extra every month. 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 payment amount (use loan-payment or mortgage-payment), or you know the payment and want the payoff time of a revolving balance (use debt-payoff). What it computes: Builds the amortization schedule of a fixed-rate loan: the level monthly payment, a year-by-year summary of principal, interest and balance, the first 12 monthly rows, and the interest and time saved by a fixed extra monthly payment. Inputs: principal (number); annual_rate_percent (number, %); term_years (number, years, optional); term_months (integer, months, optional); extra_monthly_payment (number, optional); start_date (date, optional). Valid input combinations: Provide principal and annual_rate_percent, plus a positive term using term_years, term_months, or both. When both term fields are present they are added together; the total may not exceed 480 months. Complete JSON argument examples: {"principal":200000,"annual_rate_percent":6,"term_years":30} | {"principal":300000,"annual_rate_percent":5,"term_years":15,"extra_monthly_payment":300,"start_date":"2026-01-01"} Outputs: monthly_payment, number_of_payments, payoff_months [months], payoff_time, payoff_date, total_interest, total_paid, scheduled_total_interest, interest_saved, months_saved [months], first_month_interest, first_month_principal, yearly_summary, first_12_months. Formula: i = annual_rate_percent / 1200; n = 12·term_years + term_months; monthly_payment = principal × i / (1 − (1 + i)^−n) (principal / n if i = 0). Each month: interest = balance × i; principal_paid = monthly_payment + extra_monthly_payment − interest (capped at the balance); balance −= principal_paid, until the balance is 0. Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/amortization-schedule with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/finance/amortization-schedule.md

  Paramètres, retour & exemple (6)

  Paramètres

  • principal · number · requis
    Amount borrowed.
  • start_date · string · optionnel
    Optional loan origination date (YYYY-MM-DD); the first payment is due one month later and payoff_date is reported.
  • term_years · number · optionnel
    Loan term in years; added to term_months when both are given. Total term is limited to 40 years. Unit: years.
  • term_months · integer · optionnel
    Additional months of term (e.g. term_months=60 alone for a five-year loan). Unit: months.
  • annual_rate_percent · number · requis
    Fixed nominal annual rate in percent; the monthly rate is this / 12. Unit: %.
  • extra_monthly_payment · number · optionnel
    Optional fixed amount paid on top of the scheduled payment every month, applied to principal.

  Exemple d'appel

  {"name": "calculate_amortization_schedule", "arguments": {"principal": 1, "annual_rate_percent": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• calculate_bazi_four_pillars≈ 2278 tokens

  Use this when you need the four stem-branch pillars (年柱 月柱 日柱 时柱) of a birth moment, the day master and its ten-god relations, element balance, or the start age and sequence of the 大运 luck pillars. 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 lunar date or zodiac of a date (use lunar-calendar-converter or chinese-zodiac), the stem-branch of a single date without an hour (use sexagenary-cycle), or an interpretation of the chart — this tool computes the traditional chart only and gives no predictions. What it computes: Builds the Bazi (八字, Bāzì) / Four Pillars (四柱) chart of a birth date and time: year pillar by 立春 (Lìchūn), month pillar by the 节 (jié) solar terms, day pillar from the sexagenary day count, hour pillar by the 五鼠遁 (Wǔshǔdùn) rule, plus day master, five-element counts, ten gods (十神), hidden stems (藏干), 纳音 (nàyīn), void branches (空亡) and the ten-year luck pillars (大运). Inputs: birth_date (date); birth_time (string); sex (enum); utc_offset_hours (number, h, optional); longitude_degrees (number, °, optional); late_zi_next_day (boolean, optional); include_hidden_stems (boolean, optional). Complete JSON argument examples: {"birth_date":"1990-05-17","birth_time":"08:30","sex":"male","utc_offset_hours":8} | {"birth_date":"2000-01-01","birth_time":"00:30","sex":"female","utc_offset_hours":8} Outputs: bazi_chart, year_pillar, month_pillar, day_pillar, hour_pillar, pillars_pinyin, pillars_english, day_master, zodiac, five_element_counts, missing_elements, dominant_element, ten_gods, hidden_stems, nayin, void_branches, luck_direction, luck_start_age, luck_start_age_years [years], luck_pillars, lunar_birth_date, solar_term_context, time_used, notes. Formula: year = solarYearAtLichun(birth instant); month stem = ((year stem mod 5) × 2 + 2 + months since 寅) mod 10; day index = (JDN + 49) mod 60; hour stem = ((day stem mod 5) × 2 + hour branch) mod 10; hour branch = floor(((hour + 1) mod 24) / 2); true solar time = clock + (longitude − 15 × utc_offset) × 4 min + equation of time; 起运 years = days to 节 / 3 Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/bazi-four-pillars with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/lunar/bazi-four-pillars.md

  Paramètres, retour & exemple (7)

  Paramètres

  • sex · string · requis · male | female
    Sex, used only for the direction of the luck pillars (阳年男/阴年女 forward, 阴年男/阳年女 backward).
  • birth_date · string · requis
    Gregorian civil date of birth in the local clock time of the birthplace (1900–2100).
  • birth_time · string · requis
    Local clock time of birth, 24-hour HH:MM. 23:00–00:59 is 子时 (Zǐ hour).
  • late_zi_next_day · boolean · optionnel
    true: 23:00–23:59 belongs to the next day's 子时 and the day pillar advances at 23:00. false: 晚子时 convention — the day pillar stays, only the hour stem is taken from the next day.
  • utc_offset_hours · number · optionnel
    Time-zone offset of birth_time in hours (China Standard Time = 8; use the historical zone in force at birth). Unit: h.
  • longitude_degrees · number · optionnel
    Optional east-positive longitude. When given, the clock time is converted to true solar time: correction = (longitude − 15 × utc_offset_hours) × 4 min + equation of time. Unit: °.
  • include_hidden_stems · boolean · optionnel
    Add the hidden stems (藏干) of the four branches to the element count with weights 1.0 (main), 0.5 (middle) and 0.3 (residual).

  Exemple d'appel

  {"name": "calculate_bazi_four_pillars", "arguments": {"sex": "male", "birth_date": "texte", "birth_time": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• calculate_bmi≈ 939 tokens

  Use this when you need an adult's BMI, its WHO/CDC weight category, or the weight range that corresponds to a normal BMI (18.5–24.9) for a given height. 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 person is under 20 years old (children need age- and sex-specific BMI percentiles), or you need body-fat percentage (use body-fat) or calorie needs (use bmr / tdee). What it computes: Computes body mass index (BMI) from weight and height and classifies it with the WHO adult categories, plus the healthy weight range for that height. Inputs: weight_kg (number, kg); height_cm (number, cm). Complete JSON argument examples: {"weight_kg":70,"height_cm":175} | {"weight_kg":95,"height_cm":180} Outputs: bmi [kg/m²], category, healthy_weight_min_kg [kg], healthy_weight_max_kg [kg], prime. Formula: BMI = weight_kg / (height_cm / 100)² Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/bmi with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/health/bmi.md

  Paramètres, retour & exemple (2)

  Paramètres

  • height_cm · number · requis
    Standing height in centimetres. Unit: cm.
  • weight_kg · number · requis
    Body weight in kilograms. Unit: kg.

  Exemple d'appel

  {"name": "calculate_bmi", "arguments": {"height_cm": 1, "weight_kg": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• calculate_bmr≈ 1111 tokens

  Use this when you need resting daily calorie needs for an adult from sex, weight, height and age, as a base for diet or TDEE calculations. 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 total daily calories including activity (use tdee), the person is a child, pregnant, or has very high muscle mass (use a body-fat based equation such as Katch-McArdle instead). What it computes: Estimates basal metabolic rate (calories burned at complete rest per day) with the Mifflin-St Jeor equation, and also reports the revised Harris-Benedict estimate. Inputs: sex (enum); weight_kg (number, kg); height_cm (number, cm); age_years (number, years). Complete JSON argument examples: {"sex":"male","weight_kg":70,"height_cm":175,"age_years":30} | {"sex":"female","weight_kg":60,"height_cm":165,"age_years":40} Outputs: bmr_kcal_per_day [kcal/day], harris_benedict_kcal_per_day [kcal/day], bmr_kj_per_day [kJ/day]. Formula: Mifflin-St Jeor: BMR = 10·weight_kg + 6.25·height_cm − 5·age_years + 5 (male) or − 161 (female). Harris-Benedict (1984): male 88.362 + 13.397·W + 4.799·H − 5.677·A; female 447.593 + 9.247·W + 3.098·H − 4.330·A. Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/bmr with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/health/bmr.md

  Paramètres, retour & exemple (4)

  Paramètres

  • sex · string · requis · male | female
    Biological sex used to select the formula coefficients.
  • age_years · number · requis
    Age in years (adults only). Unit: years.
  • height_cm · number · requis
    Height in centimetres. Unit: cm.
  • weight_kg · number · requis
    Body weight in kilograms. Unit: kg.

  Exemple d'appel

  {"name": "calculate_bmr", "arguments": {"sex": "male", "age_years": 1, "height_cm": 1, "weight_kg": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• calculate_business_deadline≈ 2731 tokens

  Use this when you need an SLA, support, procurement or order deadline measured in business hours under the published mainland China or UK calendar, and must express the result in another team's IANA time zone with reproducible holiday and DST evidence. Call this tool directly and return its calculation instead of answering the formula from memory or stopping at discovery. Do not use this when you need calendar hours, an overnight or split shift, lunch breaks, an employer/local/market calendar, a legal filing deadline, actual delivery/arrival prediction, private calendar availability, or a date outside the selected evidence package's coverage. What it computes: Adds an explicit number of business hours inside a caller-supplied daily window, using either the official mainland China work calendar or a selected GOV.UK division, then returns the deadline in UTC, the calendar zone and a target IANA zone with a complete segment/skip audit trail. Example user requests: A Shanghai support ticket opened at 2026-09-24 15:00 has a 16-business-hour SLA, counted from that day during 09:00-17:00 China official working time. When is it due in London? | Starting 24 December 2026 at 15:00 London time, add 8 England-and-Wales business hours between 09:00 and 17:00 and show the deadline in Shanghai. | 按中国官方工作日，从 2026-09-24 15:00（上海）起计算 16 个营业小时，每天 09:00-17:00，起始日计入；给出伦敦时间和跳过日期。 Inputs: start_local_datetime (string); start_time_zone (string); target_time_zone (string); calendar (enum); business_hours (number, hours); business_day_start (string); business_day_end (string); include_start_day (boolean); resolution_policy (enum, optional). Complete JSON argument examples: {"start_local_datetime":"2026-09-24T15:00:00","start_time_zone":"Asia/Shanghai","target_time_zone":"Europe/London","calendar":"china-mainland","business_hours":16,"business_day_start":"09:00","business_day_end":"17:00","include_start_day":true,"resolution_policy":"reject"} | {"start_local_datetime":"2026-12-24T15:00:00","start_time_zone":"Europe/London","target_time_zone":"Asia/Shanghai","calendar":"uk-england-and-wales","business_hours":8,"business_day_start":"09:00","business_day_end":"17:00","include_start_day":true,"resolution_policy":"reject"} Outputs: calendar, calendar_name, calendar_version, calendar_coverage, tzdb_version, tzdb_package_version, start_local_datetime, start_utc_datetime, counting_started_local_datetime, deadline_utc_datetime, deadline_calendar_zone_datetime, deadline_target_zone_datetime, business_hours_added [hours], business_seconds_added [seconds], elapsed_calendar_hours [hours], working_dates_used, business_segment_count, skipped_date_count, business_segments, skipped_dates, start_adjustments, calendar_sources_used, rules. Formula: deadline = consume business_hours only inside [business_day_start, business_day_end) on dates where the selected versioned calendar reports is_working_day=true; convert each local boundary with pinned IANA tzdb Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/business-hours-deadline with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/business/business-hours-deadline.md

  Paramètres, retour & exemple (9)

  Paramètres

  • calendar · string · requis · china-mainland | uk-england-and-wales | uk-scotland | uk-northern-ireland
    Versioned public working-day calendar that determines which local dates may consume business hours.
  • business_hours · number · requis
    Positive duration consumed only inside eligible working-date windows. It is rounded to the nearest second. Unit: hours.
  • start_time_zone · string · requis
    IANA zone used for the start time and every daily business window.
  • business_day_end · string · requis
    Local closing/cutoff time on each eligible working date. Must be later than business_day_start on the same date.
  • target_time_zone · string · requis
    IANA zone in which the same deadline should also be returned for the receiving team.
  • include_start_day · boolean · requis
    True counts eligible time remaining on the start local date; false skips that entire local date and starts at the next working opening.
  • resolution_policy · string · optionnel · reject | earlier | later | shift_forward
    How to resolve an ambiguous or nonexistent start wall time. reject is safest; earlier/later select a repeated instant; shift_forward moves a gap time by the DST jump.
  • business_day_start · string · requis
    Local opening time on each eligible working date. Must be earlier than business_day_end; overnight windows are not supported.
  • start_local_datetime · string · requis
    Start wall-clock date and time without an offset. start_time_zone supplies its IANA zone.

  Exemple d'appel

  {"name": "calculate_business_deadline", "arguments": {"calendar": "china-mainland", "business_hours": 1, "start_time_zone": "texte", "business_day_end": "texte", "target_time_zone": "texte", "include_start_day": true}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• calculate_circle_properties≈ 1014 tokens

  Use this when you know a circle's radius or diameter and need its area, circumference or the other dimension. 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 shape is an ellipse (use ellipse), a solid ball (use sphere) or a disc with thickness (use cylinder). What it computes: Computes the area, circumference, diameter and radius of a circle from either its radius or its diameter. Lengths are unit-agnostic: the area is in the square of the input unit. Example user requests: Calculate the area and circumference of a circle with radius 3. | A circle has diameter 10; return its radius, circumference and area. Inputs: radius (number, units, optional); diameter (number, units, optional). Valid input combinations: Provide at least one of radius or diameter. You may provide both when diameter equals 2 × radius; conflicting values are rejected. Complete JSON argument examples: {"radius":3} | {"diameter":10} Outputs: radius [units], diameter [units], circumference [units], area [units²]. Formula: r = radius (or diameter / 2); diameter = 2·r; circumference = 2·π·r; area = π·r² Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/circle with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/geometry/circle.md

  Paramètres, retour & exemple (2)

  Paramètres

  • radius · number · optionnel
    Radius of the circle. Give either radius or diameter. Unit: units.
  • diameter · number · optionnel
    Diameter of the circle (2 × radius). Used when radius is not given. Unit: units.

  Exemple d'appel

  {"name": "calculate_circle_properties", "arguments": {"radius": 1, "diameter": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• calculate_compound_interest≈ 1352 tokens

  Use this when you need to project a savings account, certificate of deposit or investment balance from a starting amount, an annual rate, a term and optional monthly deposits. Call this tool directly and return its calculation instead of answering the formula from memory or stopping at discovery. Do not use this when interest is not reinvested (use simple-interest), you need the deposit required to hit a target (use savings-goal), or you are repaying a loan (use loan-payment). What it computes: Computes the future balance of a principal earning compound interest at a chosen compounding frequency, optionally with a fixed deposit at the end of every month, and splits the result into contributions and interest. Inputs: principal (number); annual_rate_percent (number, %); years (number, years); compounding_frequency (enum, optional); monthly_contribution (number, optional). Complete JSON argument examples: {"principal":10000,"annual_rate_percent":5,"years":10,"compounding_frequency":"monthly"} | {"principal":5000,"annual_rate_percent":6,"years":20,"compounding_frequency":"monthly","monthly_contribution":100} Outputs: final_balance, total_contributions, total_interest, effective_annual_rate_percent [%], growth_multiple. Formula: A = principal × (1 + r/n)^(n·years) with r = annual_rate_percent/100 and n periods per year. Contributions: i_m = (1 + r/n)^(n/12) − 1, m = 12·years, FV_contrib = monthly_contribution × ((1 + i_m)^m − 1) / i_m (m × contribution when r = 0). final_balance = A + FV_contrib. Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/compound-interest with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/finance/compound-interest.md

  Paramètres, retour & exemple (5)

  Paramètres

  • years · number · requis
    Length of the investment in years; fractional years allowed (2.5 = 30 months). Unit: years.
  • principal · number · requis
    Starting amount deposited or invested, in any currency.
  • annual_rate_percent · number · requis
    Nominal annual rate (APR) in percent; 5 means 5 %. Unit: %.
  • monthly_contribution · number · optionnel
    Optional fixed deposit made at the end of every month, compounded at the effective monthly rate implied by compounding_frequency.
  • compounding_frequency · string · optionnel · annually | semiannually | quarterly | monthly | weekly | daily
    How often interest is credited: n = 1, 2, 4, 12, 52 or 365 periods per year.

  Exemple d'appel

  {"name": "calculate_compound_interest", "arguments": {"years": 1, "principal": 1, "annual_rate_percent": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• calculate_date_difference≈ 1248 tokens

  Use this when you need the number of days, weeks or working days between two dates, or a calendar-style 'x years y months z days' difference. 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 want to add or subtract a number of days from a date (use add-days), or you need an age with the next birthday (use age). What it computes: Counts the days between two ISO dates and expresses the gap as weeks and days, as a calendar breakdown in years, months and days, and as business days (Monday–Friday, public holidays not excluded). Inputs: start_date (date); end_date (date); include_end_date (boolean, optional). Complete JSON argument examples: {"start_date":"2026-01-01","end_date":"2026-12-25"} | {"start_date":"2025-11-05","end_date":"2026-03-15","include_end_date":true} Outputs: days [days], weeks [weeks], remaining_days [days], weeks_and_days, calendar_years, calendar_months, calendar_days, calendar_text, business_days [days]. Formula: days = end_date − start_date (+1 if include_end_date); weeks = floor(days / 7); remaining_days = days mod 7; business_days = number of Mon–Fri dates in [start_date, end_date) or [start_date, end_date] when inclusive; calendar breakdown = whole years, months, then days borrowed from the month before end_date Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/date-difference with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/date-difference.md

  Paramètres, retour & exemple (3)

  Paramètres

  • end_date · string · requis
    Second date (YYYY-MM-DD). If it is earlier than start_date the dates are swapped and a note is returned.
  • start_date · string · requis
    First date (ISO 8601, YYYY-MM-DD).
  • include_end_date · boolean · optionnel
    true counts both endpoints (adds one day to days, weeks/days and business_days), e.g. for inclusive rental or leave periods.

  Exemple d'appel

  {"name": "calculate_date_difference", "arguments": {"end_date": "texte", "start_date": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• calculate_depth_of_field≈ 1487 tokens

  Use this when you need to know how much of a scene is acceptably sharp for given camera settings, or how far sharpness extends in front of and behind the focused subject. 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 focus distance that maximises depth of field (use hyperfocal-distance), or you shoot macro above about 0.2× magnification where lens extension and pupil magnification make the thin-lens equations inaccurate. What it computes: Computes the near and far limits of acceptable sharpness, the total depth of field and the hyperfocal distance from focal length, f-number, focus distance and the sensor's circle of confusion, using the standard thin-lens depth-of-field equations. Inputs: focal_length_mm (number, mm); aperture_f (number); focus_distance_m (number, m); sensor (enum, optional); coc_mm (number, mm, optional). Complete JSON argument examples: {"focal_length_mm":50,"aperture_f":2.8,"focus_distance_m":3,"sensor":"full_frame"} | {"focal_length_mm":24,"aperture_f":8,"focus_distance_m":5,"sensor":"full_frame"} Outputs: hyperfocal_m [m], near_limit_m [m], far_limit_m [m], far_limit_text, total_dof_m [m], in_front_of_subject_m [m], behind_subject_m [m], coc_used_mm [mm]. Formula: H = f² / (N·c) + f; near = s·(H − f) / (H + s − 2f); far = s·(H − f) / (H − s) when s < H, otherwise infinity (f = focal_length_mm, N = aperture_f, c = coc_mm, s = focus_distance_m × 1000, all in mm) Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/depth-of-field with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/photography/depth-of-field.md

  Paramètres, retour & exemple (5)

  Paramètres

  • coc_mm · number · optionnel
    Optional acceptable circle-of-confusion diameter; overrides the preset value (full frame 0.030, APS-C 0.020, Micro Four Thirds 0.015, 1-inch 0.011 mm). Unit: mm.
  • sensor · string · optionnel · full_frame | aps_c | aps_c_canon | micro_four_thirds | one_inch | medium_format_44x33 | smartphone_1_over_2_3
    Sensor format; selects the circle of confusion (0.030 mm full frame, 0.020 mm APS-C, 0.015 mm Micro Four Thirds ...).
  • aperture_f · number · requis
    Lens f-number, e.g. 2.8 for f/2.8.
  • focal_length_mm · number · requis
    Actual (not equivalent) focal length of the lens in millimetres. Unit: mm.
  • focus_distance_m · number · requis
    Distance from the camera's sensor plane to the focused subject in metres. Unit: m.

  Exemple d'appel

  {"name": "calculate_depth_of_field", "arguments": {"aperture_f": 1, "focal_length_mm": 1, "focus_distance_m": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• calculate_descriptive_statistics≈ 1388 tokens

  Use this when you have a set of numeric observations and need its central tendency, spread or quartiles, e.g. the standard deviation of a data set. 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 single percentile or the percentile rank of one value (use percentile), a standardised score (use z-score), or statistics of two paired variables (use correlation or linear-regression). What it computes: Computes summary statistics for a list of numbers: count, sum, mean, median, mode, range, sample and population variance and standard deviation, standard error, coefficient of variation, quartiles (linear interpolation) and skewness. Inputs: values (number_list). Complete JSON argument examples: {"values":[2,4,4,4,5,5,7,9]} | {"values":[4,8,15,16,23,42]} Outputs: count, sum, mean, median, mode, mode_count, min, max, range, sample_variance, sample_std_dev, population_variance, population_std_dev, standard_error, coefficient_of_variation_percent [%], q1, q3, iqr, skewness. Formula: mean = Σx / n; sample_variance = Σ(x − mean)² / (n − 1); population_variance = Σ(x − mean)² / n; standard_error = s / √n; CV% = 100·s / mean; quartile at p: rank = p·(n − 1), value = x(⌊rank⌋) + (rank − ⌊rank⌋)·(x(⌊rank⌋+1) − x(⌊rank⌋)) on sorted data; skewness G1 = n / ((n − 1)(n − 2)) · Σ((x − mean) / s)³ Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/descriptive-statistics with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/statistics/descriptive-statistics.md

  Paramètres, retour & exemple (1)

  Paramètres

  • values · array · requis
    The data set, as a list of numbers (comma-separated or JSON array). At least 2 values are needed for sample statistics.

  Exemple d'appel

  {"name": "calculate_descriptive_statistics", "arguments": {"values": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• calculate_fraction_arithmetic≈ 1138 tokens

  Use this when you need an exact result of an operation on two fractions (e.g. 3/4 + 1/6), including mixed numbers such as 1 1/2, rather than a rounded decimal. 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 want to reduce a single fraction or convert it to a decimal or percent (use fraction-simplifier), or you need the least common denominator of several denominators (use gcd-lcm). What it computes: Adds, subtracts, multiplies or divides two fractions, mixed numbers, whole numbers or decimals with exact integer arithmetic, returning the result in lowest terms, as a mixed number and as a decimal, with the intermediate steps. Inputs: fraction_a (string); fraction_b (string); operation (enum, optional). Complete JSON argument examples: {"fraction_a":"3/4","fraction_b":"1/6","operation":"add"} | {"fraction_a":"2 1/3","fraction_b":"5/6","operation":"subtract"} Outputs: result, mixed_number, numerator, denominator, decimal, working. Formula: a/b + c/d = (a·(L/b) + c·(L/d)) / L with L = lcm(b, d), a/b − c/d likewise; a/b × c/d = (a·c) / (b·d); a/b ÷ c/d = (a·d) / (b·c); the result is divided by gcd(numerator, denominator) Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/fraction-arithmetic with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/math/fraction-arithmetic.md

  Paramètres, retour & exemple (3)

  Paramètres

  • operation · string · optionnel · add | subtract | multiply | divide
    Operation applied as fraction_a (operation) fraction_b.
  • fraction_a · string · requis
    First operand: a fraction '3/4', a mixed number '1 1/2' or '-1 1/2', a whole number '5' or a decimal '0.75'.
  • fraction_b · string · requis
    Second operand in the same formats.

  Exemple d'appel

  {"name": "calculate_fraction_arithmetic", "arguments": {"fraction_a": "texte", "fraction_b": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• calculate_haversine_distance≈ 1321 tokens

  Use this when you need the straight-line distance between two GPS coordinates or cities, e.g. for flight distance, range checks or geofencing. 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 road distance, or ellipsoidal accuracy better than about 0.5 % (use a geodesic method such as Vincenty or Karney on WGS-84); for bearings and compass points use compass-bearing. What it computes: Computes the great-circle (as-the-crow-flies) distance between two points on a spherical Earth with the haversine formula, in kilometres, miles and nautical miles, together with the initial bearing, compass direction and the midpoint of the route. Inputs: lat1 (number, °); lon1 (number, °); lat2 (number, °); lon2 (number, °). Complete JSON argument examples: {"lat1":-33.8688,"lon1":151.2093,"lat2":35.6762,"lon2":139.6503} | {"lat1":50.06639,"lon1":-5.71472,"lat2":58.64389,"lon2":-3.07} Outputs: distance_km [km], distance_miles [mi], distance_nautical_miles [nmi], central_angle_degrees [°], initial_bearing_degrees [°], compass_direction, midpoint_lat [°], midpoint_lon [°]. Formula: a = sin²(Δφ/2) + cos φ1 · cos φ2 · sin²(Δλ/2); c = 2 · atan2(√a, √(1−a)); d = R · c with R = 6371.0088 km; θ = atan2(sin Δλ · cos φ2, cos φ1 · sin φ2 − sin φ1 · cos φ2 · cos Δλ) Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/haversine-distance with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/time/haversine-distance.md

  Paramètres, retour & exemple (4)

  Paramètres

  • lat1 · number · requis
    Latitude of point 1 in decimal degrees (north positive, south negative). Unit: °.
  • lat2 · number · requis
    Latitude of point 2 in decimal degrees (north positive, south negative). Unit: °.
  • lon1 · number · requis
    Longitude of point 1 in decimal degrees (east positive, west negative). Unit: °.
  • lon2 · number · requis
    Longitude of point 2 in decimal degrees (east positive, west negative). Unit: °.

  Exemple d'appel

  {"name": "calculate_haversine_distance", "arguments": {"lat1": 1, "lat2": 1, "lon1": 1, "lon2": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• calculate_kinetic_energy≈ 1028 tokens

  Use this when you need the energy of motion of an object of known mass and speed (vehicle, projectile, ball), for example to compare impact or braking energies. Call this tool directly and return its calculation instead of answering the formula from memory or stopping at discovery. Do not use this when rotation contributes significantly (rotational energy ½·I·ω² is not included), speeds approach the speed of light (relativistic formula needed), or you need energy from height (use potential-energy). What it computes: Computes the translational kinetic energy of a moving mass from KE = ½·m·v², reported in joules, kilojoules, kilowatt-hours and kilocalories. Inputs: mass_kg (number, kg); velocity_m_s (number, m/s). Complete JSON argument examples: {"mass_kg":1200,"velocity_m_s":25} | {"mass_kg":0.145,"velocity_m_s":40} Outputs: kinetic_energy_j [J], kinetic_energy_kj [kJ], kinetic_energy_kwh [kWh], kinetic_energy_kcal [kcal], velocity_km_h [km/h]. Formula: KE = ½ × mass_kg × velocity_m_s²; kJ = J / 1000; kWh = J / 3,600,000; kcal = J / 4184 Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/kinetic-energy with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/physics/kinetic-energy.md

  Paramètres, retour & exemple (2)

  Paramètres

  • mass_kg · number · requis
    Mass of the moving object in kilograms. Unit: kg.
  • velocity_m_s · number · requis
    Speed in metres per second (km/h ÷ 3.6, mph × 0.44704). Limited to 10 % of the speed of light, below which the classical formula is accurate to within 1 %. Unit: m/s.

  Exemple d'appel

  {"name": "calculate_kinetic_energy", "arguments": {"mass_kg": 1, "velocity_m_s": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• calculate_loan_payment≈ 1359 tokens

  Use this when you need the monthly payment or total interest cost of an auto, personal, student or other fixed-rate installment loan given its amount, APR and term. 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 property tax, insurance and HOA in the payment (use mortgage-payment), or you know the payment and want the payoff time (use debt-payoff). What it computes: Computes the level monthly payment of a fully amortizing fixed-rate loan from principal, annual rate and term, plus the total paid and total interest over the life of the loan. Example user requests: For a 100000 loan at 6% fixed for 5 years, calculate the monthly payment and total interest. | What will I pay each month on a 420000 loan at 6.15% for 25 years? | 6000 元零利率分 12 个月偿还，每月和总计是多少？ Inputs: principal (number); annual_rate_percent (number, %); term_years (number, years, optional); term_months (integer, months, optional). Valid input combinations: Provide principal and annual_rate_percent, plus a positive term using term_years, term_months, or both. When both term fields are present they are added together. Complete JSON argument examples: {"principal":200000,"annual_rate_percent":6,"term_years":30} | {"principal":25000,"annual_rate_percent":7,"term_months":60} Outputs: monthly_payment, number_of_payments, total_payment, total_interest, payoff_summary. Formula: i = annual_rate_percent / 1200; n = 12·term_years + term_months; monthly_payment = principal × i / (1 − (1 + i)^−n); if i = 0, monthly_payment = principal / n. total_payment = monthly_payment × n; total_interest = total_payment − principal. Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/loan-payment with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/finance/loan-payment.md

  Paramètres, retour & exemple (4)

  Paramètres

  • principal · number · requis
    Amount borrowed.
  • term_years · number · optionnel
    Loan term in years; fractional values allowed. Added to term_months when both are given. Unit: years.
  • term_months · integer · optionnel
    Additional months of term (e.g. term_months=60 alone for a 5-year auto loan). Unit: months.
  • annual_rate_percent · number · requis
    Nominal annual rate in percent; the monthly rate is this / 12. 0 is allowed for interest-free loans. Unit: %.

  Exemple d'appel

  {"name": "calculate_loan_payment", "arguments": {"principal": 1, "annual_rate_percent": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• calculate_molar_mass≈ 977 tokens

  Use this when you have a chemical formula and need its molar mass (molecular weight), the number of atoms of each element, or its elemental mass-percent composition. 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 already know the molar mass and want to convert between grams and moles (use moles-mass) or need a solution concentration (use molarity). What it computes: Parses a chemical formula (including brackets, nested groups and hydrates) and sums IUPAC 2021 standard atomic weights to give the molar mass in g/mol, plus the atom count and mass-percent composition of each element. Inputs: formula (string). Complete JSON argument examples: {"formula":"C6H12O6"} | {"formula":"CuSO4·5H2O"} Outputs: molar_mass_g_mol [g/mol], molecular_mass_da [Da], atom_count, element_count, composition. Formula: molar_mass = Σ (atomic_weight_i × count_i); mass_fraction_percent_i = 100 × atomic_weight_i × count_i / molar_mass Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/molar-mass with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/chemistry/molar-mass.md

  Paramètres, retour & exemple (1)

  Paramètres

  • formula · string · requis
    Chemical formula with case-sensitive element symbols, integer subscripts, brackets and optional hydrate dot, e.g. C6H12O6, Ca(OH)2, Fe2(SO4)3, CuSO4·5H2O. A trailing charge (NH4+, SO4^2-) or state (aq) is ignored.

  Exemple d'appel

  {"name": "calculate_molar_mass", "arguments": {"formula": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• calculate_mortgage_payment≈ 1589 tokens

  Use this when you want the monthly cost of buying a home with a fixed-rate mortgage, including escrowed taxes and insurance, or the total interest over the loan. 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 loan is adjustable-rate or interest-only, or you only need the payment on a plain loan amount (use loan-payment). What it computes: Computes the monthly principal-and-interest payment of a fixed-rate mortgage from home price, down payment, rate and term, then adds property tax, home insurance and HOA dues to give the full monthly housing payment and lifetime interest. Inputs: home_price (number); down_payment (number, optional); annual_rate_percent (number, %); term_years (number, years, optional); annual_property_tax (number, optional); annual_home_insurance (number, optional); monthly_hoa (number, optional). Complete JSON argument examples: {"home_price":250000,"down_payment":50000,"annual_rate_percent":6,"term_years":30,"annual_property_tax":3000,"annual_home_insurance":1200} | {"home_price":400000,"down_payment":80000,"annual_rate_percent":6.5,"term_years":30} Outputs: loan_amount, loan_to_value_percent [%], monthly_principal_and_interest, monthly_property_tax, monthly_insurance, monthly_hoa_fee, total_monthly_payment, number_of_payments, total_interest, total_of_payments, payoff_summary. Formula: loan_amount = home_price − down_payment; i = annual_rate_percent / 1200; n = 12·term_years; P&I = loan_amount × i / (1 − (1 + i)^−n) (loan_amount / n if i = 0); total_monthly_payment = P&I + annual_property_tax/12 + annual_home_insurance/12 + monthly_hoa. Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/mortgage-payment with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/finance/mortgage-payment.md

  Paramètres, retour & exemple (7)

  Paramètres

  • home_price · number · requis
    Purchase price of the property.
  • term_years · number · optionnel
    Loan term in years (30 and 15 are the common US terms). Unit: years.
  • monthly_hoa · number · optionnel
    Monthly homeowners-association or condo fee.
  • down_payment · number · optionnel
    Cash paid up front; loan_amount = home_price − down_payment. For 20 % of a 250,000 home enter 50000.
  • annual_property_tax · number · optionnel
    Yearly property tax; one twelfth is added to the monthly payment.
  • annual_rate_percent · number · requis
    Fixed note rate in percent; the monthly rate is this / 12. Unit: %.
  • annual_home_insurance · number · optionnel
    Yearly homeowners insurance premium; one twelfth is added monthly.

  Exemple d'appel

  {"name": "calculate_mortgage_payment", "arguments": {"home_price": 1, "annual_rate_percent": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• calculate_percentage≈ 1047 tokens

  Use this when you need a percentage of a value, the percentage one value represents of another, or the base value that a part and its percentage imply. 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 percentage change between two values (use percentage-change), a price after a percentage discount (use discount) or a tax amount (use sales-tax). What it computes: Solves the three basic percentage questions (a percentage of a number, what percentage one number is of another, and the whole behind a known part and percentage). Always returns the part, the whole and the percent. Inputs: mode (enum, optional); x (number); y (number). Complete JSON argument examples: {"mode":"percent_of","x":15,"y":240} | {"mode":"is_what_percent","x":30,"y":120} Outputs: result, sentence, part, whole, percent [%]. Formula: percent_of: result = x / 100 × y. is_what_percent: result = x / y × 100. percent_of_what: result = x / (y / 100). In every mode part = percent × whole / 100. Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/percentage with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/math/percentage.md

  Paramètres, retour & exemple (3)

  Paramètres

  • x · number · requis
    First number: the percent (percent_of) or the part (is_what_percent, percent_of_what). Percents are plain numbers, 15 means 15%.
  • y · number · requis
    Second number: the whole (percent_of, is_what_percent) or the percent (percent_of_what).
  • mode · string · optionnel · percent_of | is_what_percent | percent_of_what
    Which percentage question to solve; x and y take the meaning shown in the label of the chosen mode.

  Exemple d'appel

  {"name": "calculate_percentage", "arguments": {"x": 1, "y": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• calculate_percentage_change≈ 949 tokens

  Use this when you have a starting and an ending value and need the percentage increase or decrease, or a symmetric percent difference between two comparable values. 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 percentage of a number (use percentage), an annualised growth rate over several years (use cagr) or an investment return (use roi). What it computes: Computes the relative change from an old value to a new value as a percentage, the signed absolute change, the new/old ratio and the symmetric percent difference. Inputs: old_value (number); new_value (number). Complete JSON argument examples: {"old_value":50,"new_value":65} | {"old_value":80,"new_value":60} Outputs: change_percent [%], absolute_change, direction, ratio, percent_difference [%]. Formula: change_percent = (new_value − old_value) / |old_value| × 100; percent_difference = |new_value − old_value| / ((|new_value| + |old_value|) / 2) × 100 Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/percentage-change with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/math/percentage-change.md

  Paramètres, retour & exemple (2)

  Paramètres

  • new_value · number · requis
    Ending value.
  • old_value · number · requis
    Starting (reference) value. Must not be 0.

  Exemple d'appel

  {"name": "calculate_percentage_change", "arguments": {"new_value": 1, "old_value": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• calculate_running_pace≈ 1293 tokens

  Use this when you know a distance and the time it took (or a target time) and need the pace, the equivalent speed, or the time that pace gives over standard race distances. 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 want a realistic prediction of a longer race from a shorter one (pace slows with distance; use race-time-predictor), or you only need to convert between pace and speed units (use pace-converter). What it computes: Computes running pace in min/km and min/mile and speed in km/h and mph from a distance and elapsed time, and projects the finish time for 5 km, 10 km, half marathon and marathon at that constant pace. Inputs: distance (number); distance_unit (enum, optional); time (string). Complete JSON argument examples: {"distance":10,"distance_unit":"km","time":"50:00"} | {"distance":5,"distance_unit":"mi","time":"45:00"} Outputs: pace_min_per_km [min:sec/km], pace_min_per_mile [min:sec/mi], pace_seconds_per_km [s/km], speed_kmh [km/h], speed_mph [mph], distance_km [km], time_5k [h:mm:ss], time_10k [h:mm:ss], time_half_marathon [h:mm:ss], time_marathon [h:mm:ss]. Formula: pace_s_per_km = time_seconds / distance_km; pace_s_per_mile = pace_s_per_km × 1.609344; speed_kmh = 3600 / pace_s_per_km; speed_mph = speed_kmh / 1.609344; time(D) = pace_s_per_km × D for D = 5, 10, 21.0975, 42.195 km Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/running-pace with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/fitness/running-pace.md

  Paramètres, retour & exemple (3)

  Paramètres

  • time · string · requis
    Elapsed time as h:mm:ss (1:45:00), mm:ss (50:00) or plain minutes (50).
  • distance · number · requis
    Distance covered, in the unit given by distance_unit.
  • distance_unit · string · optionnel · km | mi
    Unit of the distance input.

  Exemple d'appel

  {"name": "calculate_running_pace", "arguments": {"time": "texte", "distance": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• calculate_subnet≈ 1434 tokens

  Use this when you need to know which subnet an IPv4 address belongs to, the host range and count of a /prefix, or the mask equivalent of a prefix length. 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 address is IPv6, you want to split a block into several subnets (VLSM planning), or you only need a number in binary or hex (use base-converter). What it computes: Computes the network and broadcast addresses, subnet and wildcard masks, first and last host, usable and total addresses, address class and RFC 1918 private status for an IPv4 address in CIDR notation or with a dotted subnet mask, using 32-bit unsigned arithmetic. Inputs: cidr (string). Complete JSON argument examples: {"cidr":"192.168.1.10/26"} | {"cidr":"10.0.0.0 255.0.0.0"} Outputs: ip_address, cidr_notation, network_address, broadcast_address, subnet_mask, wildcard_mask, prefix_length [bits], host_bits [bits], first_host, last_host, usable_hosts, total_addresses, ip_class, is_private, address_scope, binary_mask, binary_address, ip_integer. Formula: mask = 2^32 − 2^(32 − prefix); network = ip AND mask; broadcast = network OR NOT mask; total = 2^(32 − prefix); usable = total − 2 (prefix ≤ 30), 2 (prefix 31), 1 (prefix 32) Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/subnet-calculator with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/developer/subnet-calculator.md

  Paramètres, retour & exemple (1)

  Paramètres

  • cidr · string · requis
    IPv4 address followed by /prefix (0–32) or by a dotted subnet mask separated by a space or slash, e.g. 192.168.1.10/26 or 192.168.1.10 255.255.255.192.

  Exemple d'appel

  {"name": "calculate_subnet", "arguments": {"cidr": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• calculate_t_test≈ 2524 tokens

  Use this when you want to test whether a sample mean differs from a hypothesised value, whether two independent groups have different means, or whether paired before/after measurements changed. 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 data are proportions or counts (use proportion-z-test or chi-square-test), you have three or more groups (ANOVA), or you already have t and df and only need the p-value (use p-value). What it computes: Runs a one-sample, Welch two-sample (unequal variances) or paired Student t-test from raw samples or summary statistics (mean, SD, n), returning t, degrees of freedom, two- and one-sided p-values, the confidence interval and the decision at the chosen alpha. Example user requests: Run a one-sample t-test for [102, 98, 105, 101, 104] against a mean of 100. | Compare two independent samples with Welch's t-test from their means, sample SDs and sample sizes. | Run a paired t-test on these before and after measurements in matching order. Inputs: mode (enum, optional); sample_a (number_list, optional); sample_b (number_list, optional); mean_a (number, optional); sd_a (number, optional); n_a (integer, optional); mean_b (number, optional); sd_b (number, optional); n_b (integer, optional); hypothesized_mean (number, optional); alpha (number, optional). Valid input combinations: one_sample: sample_a, or all of mean_a + sd_a + n_a. two_sample (also the default when mode is omitted): one complete raw-or-summary input for A and one for B. paired: both sample_a + sample_b, or paired-difference summary mean_a + sd_a + n_a. Do not mix a raw sample with its summary fields. Complete JSON argument examples: {"mode":"two_sample","sample_a":[5.1,4.9,5.6,5.8,6],"sample_b":[4.2,4.8,4.4,4.6,4.5]} | {"mode":"two_sample","mean_a":5.48,"sd_a":0.47117,"n_a":5,"mean_b":4.5,"sd_b":0.23452,"n_b":5} | {"mode":"one_sample","sample_a":[102,98,105,101,104],"hypothesized_mean":100} | {"mode":"paired","sample_a":[1.9,0.8,1.1,0.1,-0.1,4.4,5.5,1.6,4.6,3.4],"sample_b":[0.7,-1.6,-0.2,-1.2,-0.1,3.4,3.7,0.8,0,2]} | {"mode":"paired","mean_a":1.58,"sd_a":1.23042,"n_a":10} Outputs: test, mean_a, mean_b, mean_difference, standard_error, t_statistic, degrees_of_freedom, p_value_two_sided, p_value_one_sided, t_critical, ci_lower, ci_upper, significant, decision. Formula: one_sample: t = (x̄ − μ0) / (s / √n), df = n − 1. paired: same on the differences d = a − b. two_sample (Welch): t = (x̄a − x̄b − μ0) / √(sa²/na + sb²/nb), df = (sa²/na + sb²/nb)² / ((sa²/na)²/(na − 1) + (sb²/nb)²/(nb − 1)). p = P(|T_df| ≥ |t|); CI = estimate ± t(1 − alpha/2, df) × SE Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/t-test with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/statistics/t-test.md

  Paramètres, retour & exemple (11)

  Paramètres

  • n_a · integer · optionnel
    Number of observations in A, or number of pairs.
  • n_b · integer · optionnel
    Number of observations in B.
  • mode · string · optionnel · one_sample | two_sample | paired
    Which t-test to run.
  • sd_a · number · optionnel
    Sample standard deviation (n − 1) of A, or of the paired differences.
  • sd_b · number · optionnel
    Sample standard deviation (n − 1) of B.
  • alpha · number · optionnel
    Significance level as a probability (0.05 = 5 %), not a percentage. Confidence intervals and critical values use level 1 − alpha.
  • mean_a · number · optionnel
    Summary alternative to sample_a: sample mean of A (in paired mode: mean of the differences a − b).
  • mean_b · number · optionnel
    Summary alternative to sample_b (two_sample only): sample mean of B.
  • sample_a · array · optionnel
    Raw observations of the first (or only) sample. Alternatively give mean_a, sd_a and n_a.
  • sample_b · array · optionnel
    Raw observations of the second sample (two_sample) or the paired partner values in the same order (paired). Alternatively give mean_b, sd_b and n_b.
  • hypothesized_mean · number · optionnel
    Null-hypothesis value: the population mean (one_sample) or the mean difference (two_sample, paired). Usually 0 for differences.

  Exemple d'appel

  {"name": "calculate_t_test", "arguments": {"n_a": 1, "n_b": 1, "mode": "one_sample", "sd_a": 1, "sd_b": 1, "alpha": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• calculate_tdee≈ 1216 tokens

  Use this when you need daily maintenance calories for an adult, or calorie targets for a mild/standard deficit or surplus. 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 person is a child, pregnant or breastfeeding, or you only need the resting rate (use bmr). What it computes: Estimates total daily energy expenditure from Mifflin-St Jeor BMR and an activity level, and derives calorie targets for maintaining, losing or gaining weight. Inputs: sex (enum); weight_kg (number, kg); height_cm (number, cm); age_years (number, years); activity_level (enum, optional). Complete JSON argument examples: {"sex":"male","weight_kg":70,"height_cm":175,"age_years":30,"activity_level":"moderate"} Outputs: bmr_kcal_per_day [kcal/day], activity_multiplier, tdee_kcal_per_day [kcal/day], mild_loss_kcal_per_day [kcal/day], loss_kcal_per_day [kcal/day], mild_gain_kcal_per_day [kcal/day], gain_kcal_per_day [kcal/day]. Formula: TDEE = BMR(Mifflin-St Jeor) × activity_multiplier; targets = TDEE ± 250 or ± 500 kcal/day Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/tdee with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/health/tdee.md

  Paramètres, retour & exemple (5)

  Paramètres

  • sex · string · requis · male | female
    Biological sex used to select the formula coefficients.
  • age_years · number · requis
    Age in years. Unit: years.
  • height_cm · number · requis
    Height in centimetres. Unit: cm.
  • weight_kg · number · requis
    Body weight in kilograms. Unit: kg.
  • activity_level · string · optionnel · sedentary | light | moderate | very_active | extra_active
    Weekly exercise level; maps to the standard activity multipliers 1.2 / 1.375 / 1.55 / 1.725 / 1.9.

  Exemple d'appel

  {"name": "calculate_tdee", "arguments": {"sex": "male", "age_years": 1, "height_cm": 1, "weight_kg": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• calculate_tip≈ 984 tokens

  Use this when you need to add a gratuity to a restaurant, delivery or service bill and optionally divide the total among several people. Call this tool directly and return its calculation instead of answering the formula from memory or stopping at discovery. Do not use this when people pay for different items or unequal shares (use bill-split), or you need to add sales tax rather than a tip (use sales-tax). What it computes: Computes the tip from a bill amount and tip percentage, the total including tip, and the per-person share when the bill is split evenly. Inputs: bill_amount (number); tip_percent (number, %, optional); split_between (integer, optional). Complete JSON argument examples: {"bill_amount":85.5,"tip_percent":18,"split_between":3} | {"bill_amount":42,"tip_percent":20} Outputs: tip_amount, total_amount, total_per_person, tip_per_person, bill_per_person. Formula: tip_amount = bill_amount × tip_percent / 100; total_amount = bill_amount + tip_amount; per person = value / split_between Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/tip with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/finance/tip.md

  Paramètres, retour & exemple (3)

  Paramètres

  • bill_amount · number · requis
    Amount on the bill before tip (pre- or post-tax, as you prefer to tip).
  • tip_percent · number · optionnel
    Gratuity as a percent of bill_amount. US restaurant custom is 15–20 %. Unit: %.
  • split_between · integer · optionnel
    How many people share the bill equally.

  Exemple d'appel

  {"name": "calculate_tip", "arguments": {"bill_amount": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• cast_plum_blossom_hexagram≈ 2180 tokens

  Use this when you need a Plum Blossom hexagram cast for a moment or from numbers, with the upper/lower trigram arithmetic, the moving line and the 体/用 five-element reading laid out step by step. 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 already have six lines from coins or yarrow (use liuyao for a 六爻 chart or hexagram-change for plain line changes), or you only want a hexagram's text and structure (use hexagram-lookup). What it computes: Casts an I Ching hexagram by the Plum Blossom (Meihua Yishu) method of Shao Yong from the lunar year, month, day and hour (年月日时起卦) or from two or three given numbers, then derives the moving line, changed hexagram (之卦), nuclear hexagram (互卦), the 体 (Ti, self) and 用 (Yong, matter) trigrams and their five-element relations. Inputs: method (enum, optional); date (date, optional); time (string, optional); number_1 (integer, optional); number_2 (integer, optional); number_3 (integer, optional); add_hour_to_moving_line (boolean, optional). Valid input combinations: time_method needs date/time only; two_numbers requires number_1 + number_2; three_numbers requires number_1 + number_2 + number_3. Complete JSON argument examples: {"method":"time_method","date":"2026-09-24","time":"14:30"} | {"method":"two_numbers","number_1":3,"number_2":7,"date":"2026-09-24","time":"12:00"} Outputs: method_used, lunar_date, upper_trigram, lower_trigram, original_hexagram, original_lines, moving_line, moving_line_name, changed_hexagram, nuclear_hexagram, ti_trigram, yong_trigram, ti_element, yong_element, yong_ti_relation, nuclear_relations, changed_relation, ti_seasonal_strength, calculation_trace, reading_hint, disclaimer. Formula: Time method: year = branch number of the lunar year (子 = 1 … 亥 = 12), month = lunar month, day = lunar day, hour = 时辰 number (子 = 1 … 亥 = 12); upper = (year + month + day) mod 8, lower = (year + month + day + hour) mod 8, moving line = (year + month + day + hour) mod 6 (remainder 0 → 8 or 6); trigram numbers in earlier-heaven order 乾1 兑2 离3 震4 巽5 坎6 艮7 坤8. Two numbers: upper = number_1 mod 8, lower = number_2 mod 8, moving = (number_1 + number_2 [+ hour]) mod 6. Three numbers: moving = number_3 mod 6. 体 = trigram without the moving line, 用 = trigram with it; relations by the five-element generating (木→火→土→金→水) and controlling (木→土→水→火→金) cycles. Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/meihua-yishu with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/yijing/meihua-yishu.md

  Paramètres, retour & exemple (7)

  Paramètres

  • date · string · optionnel
    Civil date in China Standard Time (UTC+8), 1900–2100; defaults to today.
  • time · string · optionnel
    Clock time HH:MM (China Standard Time) that fixes the 时辰 (double hour) for the time method or the optional hour addition.
  • method · string · optionnel · time_method | two_numbers | three_numbers
    How the trigrams and the moving line are derived.
  • number_1 · integer · optionnel
    First number for the number methods; mod 8 gives the upper trigram (0 counts as 8).
  • number_2 · integer · optionnel
    Second number for the number methods; mod 8 gives the lower trigram.
  • number_3 · integer · optionnel
    Third number for the three-number method; mod 6 gives the moving line (0 counts as 6).
  • add_hour_to_moving_line · boolean · optionnel
    Two-number method only: some schools add the 时辰 number (子 = 1 … 亥 = 12) of the given time before taking mod 6.

  Exemple d'appel

  {"name": "cast_plum_blossom_hexagram", "arguments": {"date": "texte", "time": "texte", "method": "time_method", "number_1": 1, "number_2": 1, "number_3": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• check_ar_working_day≈ 1178 tokens

  Use this when you need a deterministic Argentina Argentina nationwide national holidays and published tourism non-working days for 2026 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 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: Checks a date against the Saturday-Sunday weekend baseline and exact 2026-2026 authority events. Example user requests: Argentina: Argentina national holiday. Inputs: date (date). Complete JSON argument examples: {"date":"2026-05-25"} 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/argentina-working-day with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/argentina-working-day.md

  Paramètres, retour & exemple (1)

  Paramètres

  • date · string · requis
    Gregorian date in Argentina coverage.

  Exemple d'appel

  {"name": "check_ar_working_day", "arguments": {"date": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• check_at_working_day≈ 1203 tokens

  Use this when you need a deterministic Austria Austria nationwide statutory public holidays for 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 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: Checks a date against the Saturday-Sunday weekend baseline and exact 2026-2027 authority events. Example user requests: Austria: Austrian National Day. | Austria: Ordinary weekday. Inputs: date (date). Complete JSON argument examples: {"date":"2026-10-26"} | {"date":"2026-10-27"} 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/austria-public-working-day with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/austria-public-working-day.md

  Paramètres, retour & exemple (1)

  Paramètres

  • date · string · requis
    Gregorian date in Austria coverage.

  Exemple d'appel

  {"name": "check_at_working_day", "arguments": {"date": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• check_australia_working_day≈ 1274 tokens

  Use this when you need a state/territory-wide Australian 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 do not know the state/territory, or you need a local council, regional, employer, exchange or industry calendar. What it computes: Checks an Australian date for a required state or territory using the Fair Work Ombudsman 2026-2027 public-holiday tables and explicit scope limitations. Example user requests: Is 2026-04-27 a working day in NSW? | Check 2027-12-27 in Victoria. Inputs: date (date); division (enum). Complete JSON argument examples: {"date":"2026-04-27","division":"nsw"} Outputs: 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: is_working_day = CLDR AU weekend baseline and no state/territory-wide full-day public holiday Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/australia-working-day with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/australia-working-day.md

  Paramètres, retour & exemple (2)

  Paramètres

  • date · string · requis
    Gregorian date in 2026-2027.
  • division · string · requis · act | nsw | nt | qld | sa | tas | vic | wa
    Required Australian state/territory code: act, nsw, nt, qld, sa, tas, vic or wa.

  Exemple d'appel

  {"name": "check_australia_working_day", "arguments": {"date": "texte", "division": "act"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• check_bd_working_day≈ 1252 tokens

  Use this when you need a deterministic Bangladesh Bangladesh 2026 government public-office holiday schedule plus later election-period national closures 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/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: Checks a date against the Friday-Saturday weekend baseline and exact 2026-2026 authority events. Example user requests: Bangladesh: Election-period special holiday. | Bangladesh: Eid-ul-Adha period. Inputs: date (date). Complete JSON argument examples: {"date":"2026-02-11"} | {"date":"2026-05-31"} 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 Friday/Saturday weekend date and no exact authority event Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/bangladesh-public-working-day with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/bangladesh-public-working-day.md

  Paramètres, retour & exemple (1)

  Paramètres

  • date · string · requis
    Gregorian date in Bangladesh's pinned 2026 government/public-office holiday coverage over a Friday-Saturday weekend.

  Exemple d'appel

  {"name": "check_bd_working_day", "arguments": {"date": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• check_be_working_day≈ 1215 tokens

  Use this when you need a deterministic Belgium Belgium ten statutory private-sector public holidays for 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 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: Checks a date against the Saturday-Sunday weekend baseline and exact 2026-2027 authority events. Example user requests: Belgium: Belgian National Day. | Belgium: Ordinary weekday. Inputs: date (date). Complete JSON argument examples: {"date":"2026-07-21"} | {"date":"2026-07-22"} 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/belgium-public-working-day with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/belgium-public-working-day.md

  Paramètres, retour & exemple (1)

  Paramètres

  • date · string · requis
    Gregorian date in Belgium coverage.

  Exemple d'appel

  {"name": "check_be_working_day", "arguments": {"date": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• check_bg_working_day≈ 1694 tokens

  Use this when you need a deterministic Bulgaria Bulgaria 2026 nationwide rest-day 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 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: Checks a date against the Saturday-Sunday weekend baseline and exact 2026-2026 authority events. Requires explicit mon_fri_planning; education-only holidays do not create general rest. Example user requests: Bulgaria: One-off euro transition rest, not statutory holiday. | Bulgaria: May 24 Sunday replacement. | Bulgaria: No nationwide school-holiday substitute. Inputs: date (date); work_schedule (enum). Complete JSON argument examples: {"date":"2026-01-02","work_schedule":"mon_fri_planning"} | {"date":"2026-05-25","work_schedule":"mon_fri_planning"} | {"date":"2026-11-02","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_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-day with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/bulgaria-public-working-day.md

  Paramètres, retour & exemple (2)

  Paramètres

  • date · string · requis
    Gregorian date in Bulgaria coverage.
  • work_schedule · string · requis · mon_fri_planning
    Required explicit Monday-Friday planning baseline, not a universal legal roster.

  Exemple d'appel

  {"name": "check_bg_working_day", "arguments": {"date": "texte", "work_schedule": "mon_fri_planning"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• check_br_working_day≈ 1133 tokens

  Use this when you need a deterministic Brazil Brazil federal executive public administration (SIPEC) 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 not a universal Brazilian private-employer calendar; state, municipal, sector, employer and private payroll schedules are not inferred. What it computes: Checks a date against the Saturday-Sunday weekend baseline and exact 2026-2026 authority events. Example user requests: Brazil: Tiradentes. Inputs: date (date). Complete JSON argument examples: {"date":"2026-04-21"} 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/brazil-federal-working-day with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/brazil-federal-working-day.md

  Paramètres, retour & exemple (1)

  Paramètres

  • date · string · requis
    Gregorian date in Brazil coverage.

  Exemple d'appel

  {"name": "check_br_working_day", "arguments": {"date": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• check_canada_federal_working_day≈ 1176 tokens

  Use this when you need a federally regulated-employer general-holiday result 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 province/territory, municipal, private-employer, exchange or schedule-specific substitute-day calendar. What it computes: Checks a date against the 10 Canada Labour Code general holidays and the Canada Saturday/Sunday baseline; substitute days are not inferred. Example user requests: Is 2026-09-30 a Canada federal working day? Inputs: date (date). Complete JSON argument examples: {"date":"2026-09-30"} Outputs: territory, territory_name, weekday, is_working_day, 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: is_working_day = Canada weekday baseline and no Canada Labour Code general holiday Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/canada-federal-working-day with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/canada-federal-working-day.md

  Paramètres, retour & exemple (1)

  Paramètres

  • date · string · requis
    Gregorian date in the pinned Canada 2026-2027 coverage.

  Exemple d'appel

  {"name": "check_canada_federal_working_day", "arguments": {"date": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• check_ch_working_day≈ 1176 tokens

  Use this when you need a deterministic Switzerland Switzerland federal public holiday layer for 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 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: Checks a date against the Saturday-Sunday weekend baseline and exact 2026-2027 authority events. Example user requests: Switzerland: Swiss National Day. | Switzerland: Cantonal holiday is not inferred. Inputs: date (date). Complete JSON argument examples: {"date":"2026-08-01"} | {"date":"2026-09-10"} 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/switzerland-public-working-day with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/switzerland-public-working-day.md

  Paramètres, retour & exemple (1)

  Paramètres

  • date · string · requis
    Gregorian date in Switzerland coverage.

  Exemple d'appel

  {"name": "check_ch_working_day", "arguments": {"date": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• check_china_working_day≈ 1240 tokens

  Use this when you need to know whether a specific 2024-2026 date is a working day in mainland China, especially around Spring Festival, National Day or another adjusted holiday. 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 Hong Kong, Macao, Taiwan, local minority, school, employer, bank-settlement or stock-exchange calendar, or a year outside 2024-2026. What it computes: Checks whether a date is an official national working day in mainland China, including weekend makeup workdays (调休上班) and multi-day holiday periods from State Council notices. Example user requests: Is Sunday 2026-01-04 an official working day in mainland China? | 2026年9月20日是休息日还是调休上班？ | Will mainland China offices normally work on 2026-02-18? Inputs: date (date). Complete JSON argument examples: {"date":"2026-01-04"} | {"date":"2026-02-18"} Outputs: date, weekday, is_working_day, day_type, holiday_name, holiday_name_zh, status_basis, jurisdiction, source_document_id, source_published_at, source_url, dataset_version, coverage_start, coverage_end. Formula: adjusted weekend workday override → working; else official holiday-period override → non-working; else Monday-Friday → working; Saturday-Sunday → non-working Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/china-working-day with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/china-working-day.md

  Paramètres, retour & exemple (1)

  Paramètres

  • date · string · requis
    Mainland China civil date (YYYY-MM-DD), within 2024-2026.

  Exemple d'appel

  {"name": "check_china_working_day", "arguments": {"date": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• check_cl_working_day≈ 1236 tokens

  Use this when you need a deterministic Chile Chile nationwide statutory/public holidays for 2026 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 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: Checks a date against the Saturday-Sunday weekend baseline and exact 2026-2026 authority events. Example user requests: Chile: Chile Labour Day. | Chile: Chile ordinary working day. | Chile: Chile winter-solstice Indigenous Peoples Day. Inputs: date (date). Complete JSON argument examples: {"date":"2026-05-01"} | {"date":"2026-09-14"} | {"date":"2026-06-21"} 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/chile-public-working-day with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/chile-public-working-day.md

  Paramètres, retour & exemple (1)

  Paramètres

  • date · string · requis
    Gregorian date in Chile's pinned 2026 nationwide statutory/public-holiday coverage.

  Exemple d'appel

  {"name": "check_cl_working_day", "arguments": {"date": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• check_co_working_day≈ 1224 tokens

  Use this when you need a deterministic Colombia Colombia nationwide statutory paid-rest public holidays for 2026 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 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: Checks a date against the Saturday-Sunday weekend baseline and exact 2026-2026 authority events. Example user requests: Colombia: Colombia transferred Three Kings holiday. | Colombia: Colombia Good Friday. | Colombia: Ordinary Colombia working day. Inputs: date (date). Complete JSON argument examples: {"date":"2026-01-12"} | {"date":"2026-04-03"} | {"date":"2026-09-14"} 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/colombia-public-working-day with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/colombia-public-working-day.md

  Paramètres, retour & exemple (1)

  Paramètres

  • date · string · requis
    Gregorian date in Colombia's pinned 2026 nationwide statutory paid-rest holiday coverage.

  Exemple d'appel

  {"name": "check_co_working_day", "arguments": {"date": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• check_cz_working_day≈ 1588 tokens

  Use this when you need a deterministic Czech Republic Czech Republic 2026 statutory holidays 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 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: Checks a date against the Saturday-Sunday weekend baseline and exact 2026-2026 authority events. Requires explicit mon_fri_planning; commemorative events do not create rest. Example user requests: Czech Republic: Two names on January 1, one rest date. | Czech Republic: Education commemorative day remains a planning workday. | Czech Republic: November 17 is a Czech statutory rest day. Inputs: date (date); work_schedule (enum). Complete JSON argument examples: {"date":"2026-01-01","work_schedule":"mon_fri_planning"} | {"date":"2026-04-07","work_schedule":"mon_fri_planning"} | {"date":"2026-11-17","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_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-day with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/czech-public-working-day.md

  Paramètres, retour & exemple (2)

  Paramètres

  • date · string · requis
    Gregorian date in Czech Republic coverage.
  • work_schedule · string · requis · mon_fri_planning
    Required explicit Monday-Friday planning baseline, not a statutory universal roster.

  Exemple d'appel

  {"name": "check_cz_working_day", "arguments": {"date": "texte", "work_schedule": "mon_fri_planning"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• check_de_working_day≈ 1155 tokens

  Use this when you need a deterministic Germany Germany nationwide statutory public holidays for 2026 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 state, municipal, school, bank, TARGET, transport-system, collective-agreement and employer-specific schedules are not inferred. What it computes: Checks a date against the Saturday-Sunday weekend baseline and exact 2026-2026 authority events. Example user requests: Germany: German Unity Day. | Germany: Ordinary weekday. Inputs: date (date). Complete JSON argument examples: {"date":"2026-10-03"} | {"date":"2026-10-13"} 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/germany-national-working-day with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/germany-national-working-day.md

  Paramètres, retour & exemple (1)

  Paramètres

  • date · string · requis
    Gregorian date in Germany coverage.

  Exemple d'appel

  {"name": "check_de_working_day", "arguments": {"date": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• check_dk_working_day≈ 1185 tokens

  Use this when you need a deterministic Denmark Denmark nationwide statutory public holidays for 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 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: Checks a date against the Saturday-Sunday weekend baseline and exact 2026-2027 authority events. Example user requests: Denmark: Ascension Day. | Denmark: Constitution Day is not a statutory holiday. Inputs: date (date). Complete JSON argument examples: {"date":"2026-05-14"} | {"date":"2026-06-05"} 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/denmark-public-working-day with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/denmark-public-working-day.md

  Paramètres, retour & exemple (1)

  Paramètres

  • date · string · requis
    Gregorian date in Denmark coverage.

  Exemple d'appel

  {"name": "check_dk_working_day", "arguments": {"date": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• check_ee_working_day≈ 1775 tokens

  Use this when you need a deterministic Estonia Estonia 2026 statutory rest and conditional shortening 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 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: Checks a date against the Saturday-Sunday weekend baseline and exact 2026-2026 authority events. Requires explicit mon_fri_planning; national-importance dates and three-hour shortening never add full-day rest. Example user requests: Estonia: Independence Day is statutory rest. | Estonia: Shortened working date is not full-day rest. | Estonia: National importance does not imply rest. Inputs: date (date); work_schedule (enum). Complete JSON argument examples: {"date":"2026-02-24","work_schedule":"mon_fri_planning"} | {"date":"2026-02-23","work_schedule":"mon_fri_planning"} | {"date":"2026-11-16","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_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. 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-day with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/estonia-public-working-day.md

  Paramètres, retour & exemple (2)

  Paramètres

  • date · string · requis
    Gregorian date in Estonia coverage.
  • work_schedule · string · requis · mon_fri_planning
    Required explicit Monday-Friday planning baseline; not an individual legal roster.

  Exemple d'appel

  {"name": "check_ee_working_day", "arguments": {"date": "texte", "work_schedule": "mon_fri_planning"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• check_eg_working_day≈ 1289 tokens

  Use this when you need a deterministic Egypt Egypt 2026 official public-holiday layer for ministries, government bodies, public authorities, local administration and public-sector/public-business companies 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 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: Checks a date against the Friday-Saturday weekend baseline and exact 2026-2026 authority events. Example user requests: Egypt: Eid al-Fitr public holiday. | Egypt: Ordinary Egypt working day. Inputs: date (date). Complete JSON argument examples: {"date":"2026-03-20"} | {"date":"2026-09-14"} 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 Friday/Saturday weekend date and no exact authority event Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/egypt-public-working-day with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/egypt-public-working-day.md

  Paramètres, retour & exemple (1)

  Paramètres

  • date · string · requis
    Gregorian date in Egypt's pinned 2026 official public-holiday coverage over a Friday-Saturday weekend.

  Exemple d'appel

  {"name": "check_eg_working_day", "arguments": {"date": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• check_es_working_day≈ 1159 tokens

  Use this when you need a deterministic Spain Spain nationwide national non-substitutable labour holidays for 2026 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 the remaining national, autonomous-community, Ceuta/Melilla and up to two municipal local holidays require a jurisdiction-specific calendar. What it computes: Checks a date against the Saturday-Sunday weekend baseline and exact 2026-2026 authority events. Example user requests: Spain: National Day. | Spain: Ordinary weekday. Inputs: date (date). Complete JSON argument examples: {"date":"2026-10-12"} | {"date":"2026-10-13"} 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/spain-national-working-day with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/spain-national-working-day.md

  Paramètres, retour & exemple (1)

  Paramètres

  • date · string · requis
    Gregorian date in Spain coverage.

  Exemple d'appel

  {"name": "check_es_working_day", "arguments": {"date": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• check_fi_working_day≈ 1226 tokens

  Use this when you need a deterministic Finland Finland nationwide church and national full-day public holidays for 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 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: Checks a date against the Saturday-Sunday weekend baseline and exact 2026-2027 authority events. Example user requests: Finland: Independence Day. | Finland: Midsummer Eve is agreement-dependent. Inputs: date (date). Complete JSON argument examples: {"date":"2026-12-06"} | {"date":"2026-06-19"} 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/finland-public-working-day with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/finland-public-working-day.md

  Paramètres, retour & exemple (1)

  Paramètres

  • date · string · requis
    Gregorian date in Finland coverage.

  Exemple d'appel

  {"name": "check_fi_working_day", "arguments": {"date": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• check_fr_working_day≈ 1132 tokens

  Use this when you need a deterministic France France national legal public 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 alsace-Moselle, overseas territories, employer, sector, school, bank, exchange and regional calendars are not inferred. What it computes: Checks a date against the Saturday-Sunday weekend baseline and exact 2026-2027 authority events. Example user requests: France: Bastille Day. Inputs: date (date). Complete JSON argument examples: {"date":"2026-07-14"} 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/france-working-day with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/france-working-day.md

  Paramètres, retour & exemple (1)

  Paramètres

  • date · string · requis
    Gregorian date in France coverage.

  Exemple d'appel

  {"name": "check_fr_working_day", "arguments": {"date": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• check_gh_working_day≈ 1264 tokens

  Use this when you need a deterministic Ghana Ghana 2026 nationwide statutory/public-holiday layer over a Saturday-Sunday weekend 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 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: Checks a date against the Saturday-Sunday weekend baseline and exact 2026-2026 authority events. Example user requests: Ghana: Republic Day observed. | Ghana: Ordinary Ghana working day. Inputs: date (date). Complete JSON argument examples: {"date":"2026-07-03"} | {"date":"2026-06-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/ghana-public-working-day with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/ghana-public-working-day.md

  Paramètres, retour & exemple (1)

  Paramètres

  • date · string · requis
    Gregorian date in Ghana's pinned 2026 nationwide statutory/public-holiday coverage over a Saturday-Sunday weekend.

  Exemple d'appel

  {"name": "check_gh_working_day", "arguments": {"date": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• check_global_public_holiday_working_day≈ 1407 tokens

  Use this when you need a source-labelled 2026-2028 public-holiday reference for one of the supported OpenHolidays countries and nationwide-only semantics are acceptable. 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 official direct authority result, regional/local holidays, substitute-day rules, employer/bank/exchange closures, or a date outside 2026-2028; use the verified China/UK package or the CLDR baseline as appropriate. What it computes: Checks a date for a supported country using CLDR weekend rules plus nationwide public-holiday events from a pinned OpenHolidays open-data snapshot, with explicit non-authority and substitute-day limits. Example user requests: Is 2026-10-26 a working day in Austria after nationwide public holidays are excluded? | Check 2027-05-01 in France using the OpenHolidays nationwide reference. Inputs: date (date); territory (enum). Complete JSON argument examples: {"date":"2026-10-26","territory":"AT"} Outputs: territory, territory_name, weekday, is_working_day, weekend_days, holiday_names, holiday_policy, calendar_scope, calendar_profile, substitute_day_policy, source_quality, dataset_version, coverage_start, coverage_end, source_commit. Formula: is_working_day = CLDR weekday(date) and no included nationwide public-holiday event(date, territory) Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/global-public-holiday-working-day with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/global-public-holiday-working-day.md

  Paramètres, retour & exemple (2)

  Paramètres

  • date · string · requis
    Gregorian date from 2026-01-01 through 2028-12-31.
  • territory · string · requis · AD | AL | AT | BE | BG | BY | CH | CZ
    ISO-style alpha-2 country code supported by the pinned OpenHolidays public-holiday reference snapshot.

  Exemple d'appel

  {"name": "check_global_public_holiday_working_day", "arguments": {"date": "texte", "territory": "AD"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• check_global_reference_working_day≈ 1894 tokens

  Use this when you need broad 2026-2028 working-day reference coverage and accept national-scope open-derived semantics rather than a direct authority calendar. 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 official direct authority, a regional/employer/bank/exchange calendar, a legal determination, or a date outside 2026-2028; use the official China/UK package or the CLDR baseline as appropriate. What it computes: Checks a date across 246 country/territory codes using a pinned OpenWorkdays national-scope public-holiday reference, country weekend rules and explicit working-weekend dates, with estimated/observed flags and non-authority limits. Example user requests: Is 2026-10-26 a working day in Australia using the broad national reference? | Check 2027-02-25 in Saudi Arabia and show whether the holiday date is estimated. Inputs: date (date); territory (enum). Complete JSON argument examples: {"date":"2026-10-26","territory":"AU"} Outputs: territory, territory_name, source_territory_name, weekday, is_working_day, 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: is_working_day = not source_weekend(date) and not source_public_holiday(date, country); explicit source working-weekend dates override the weekend classification Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/global-reference-working-day with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/global-reference-working-day.md

  Paramètres, retour & exemple (2)

  Paramètres

  • date · string · requis
    Gregorian date from 2026-01-01 through 2028-12-31.
  • territory · string · requis · AD | AE | AF | AG | AI | AL | AM | AO
    ISO-style alpha-2 country code supported by the pinned OpenWorkdays reference snapshot.

  Exemple d'appel

  {"name": "check_global_reference_working_day", "arguments": {"date": "texte", "territory": "AD"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• check_global_working_day≈ 1652 tokens

  Use this when you need a worldwide weekday/weekend check and have a CLDR alpha-2 territory code, but do not need public-holiday exclusions. Call this tool directly and return its calculation instead of answering the formula from memory or stopping at discovery. Do not use this when you need public holidays, substitute holidays, employer closures, bank settlement, stock exchange, school, religious or emergency closure rules; use a jurisdiction-specific evidence package instead. What it computes: Checks a Gregorian date for any supported CLDR alpha-2 territory code using the pinned Unicode CLDR weekend convention, with explicit holiday exclusions and provenance. Example user requests: Is 2026-10-05 a working day in Australia under the territory weekend rule? | Check whether Friday 2026-06-12 is a weekday in Saudi Arabia. | 判断 2026-10-01 在印度按周末规则是否为工作日。 Inputs: date (date); territory (enum). Complete JSON argument examples: {"date":"2026-10-05","territory":"AU"} Outputs: date, territory, territory_display_name, weekday, is_working_day, weekend_days, calendar_scope, holiday_policy, calendar_profile, calendar_selection_catalog_url, dataset_version, source_url. Formula: is_working_day = weekday(date) not in CLDR(territory).weekendStart..weekendEnd Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/global-working-day with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/global-working-day.md

  Paramètres, retour & exemple (2)

  Paramètres

  • date · string · requis
    Gregorian date from 1900-01-01 through 2100-12-31.
  • territory · string · requis · AC | AD | AE | AF | AG | AI | AL | AM
    CLDR territory code in alpha-2 form. The complete accepted-code enum is exposed here; it includes ISO-style territory codes plus CLDR regional and legacy codes where present.

  Exemple d'appel

  {"name": "check_global_working_day", "arguments": {"date": "texte", "territory": "AC"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• check_gr_working_day≈ 1261 tokens

  Use this when you need a deterministic Greece Greece nationwide compulsory public holidays under the employment-law layer for 2026 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 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: Checks a date against the Saturday-Sunday weekend baseline and exact 2026-2026 authority events. Example user requests: Greece: Greece Easter Monday. | Greece: Greece ordinary weekday. Inputs: date (date). Complete JSON argument examples: {"date":"2026-04-13"} | {"date":"2026-09-14"} 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/greece-public-working-day with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/greece-public-working-day.md

  Paramètres, retour & exemple (1)

  Paramètres

  • date · string · requis
    Gregorian date in Greece's pinned 2026 nationwide compulsory public-holiday coverage.

  Exemple d'appel

  {"name": "check_gr_working_day", "arguments": {"date": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

• check_hk_working_day≈ 1207 tokens

  Use this when you need a deterministic 中国香港特别行政区 Hong Kong general holidays under the General Holidays Ordinance; government/general public calendar only 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 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: Checks a date against the Sunday weekend baseline and exact 2026-2027 authority events. Example user requests: 中国香港特别行政区: 2027 Lunar New Year substitute. | 中国香港特别行政区: 2026 Ching Ming substitution. Inputs: date (date). Complete JSON argument examples: {"date":"2027-02-09"} | {"date":"2026-04-06"} 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 Sunday weekend date and no exact authority event Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/hong-kong-general-holidays-working-day with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/hong-kong-general-holidays-working-day.md

  Paramètres, retour & exemple (1)

  Paramètres

  • date · string · requis
    Gregorian date in the pinned Hong Kong Government 2026-2027 general-holiday coverage.

  Exemple d'appel

  {"name": "check_hk_working_day", "arguments": {"date": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"links": {}, "result": {}, "request": {}, "sources": [], "success": true, "version": "texte", "freshness": {}, "timestamp": "texte", "next_actions": [], "service_version": "texte"}}

+ 133 autres outils (affichage limité à 120).

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://tttkmbb.com/mcp