count_kz_working_days
shallowcom.tttkmbb/calcgrid · Verify this server
Use this when you need an auditable Kazakhstan working-day count. Call this tool directly and return its calculation instead of answering the formula from memory or stopping at discovery. Do not use this when this package covers the nationwide published 2026 five-day schedule over a Saturday-Sunday baseline. Six-day, shift, continuous-operation, employer, bank, school, local and sector calendars are not inferred. Qurban Ait is represented by the published 2026 first-day date. Adilet's current text records Constitution Day on 15 March with an amendment effective 2026-07-01, while the published 2026 government calendar does not add a March 15/16 closure; this package follows the published 2026 calendar and future-year packages must refresh the legal transition. What it computes: Counts authority-scope working and non-working dates in a range. Example user requests: Count Kazakhstan working days around Nauryz transfer day. | Count Kazakhstan working days around Ordinary weekday. Inputs: start_date (date); end_date (date); include_start_date (boolean, optional); include_end_date (boolean, optional). Complete JSON argument examples: {"start_date":"2026-03-21","end_date":"2026-03-25","include_start_date":true,"include_end_date":true} Outputs: working_days, non_working_days, public_holidays_counted, territory, territory_name, day_type, holiday_names, holiday_kinds, holiday_details, calendar_scope, holiday_policy, substitute_day_policy, calendar_profile, dataset_version, sources. Formula: for each included date: working_days += status.is_working_day Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/kazakhstan-public-working-days-between with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/everyday/kazakhstan-public-working-days-between.md
1 trials · measured 1 day ago
count_kz_working_days scores 100.0/100 on Vouch's measured behaviour index, from 1 real invocation trials against com.tttkmbb/calcgrid, measured 6 Oct 2026 under methodology v0.2.0. Every measured component scored 100.
Component breakdown
| Component | Weight | Value |
|---|---|---|
| Reliability | 35% | not applicable |
| Schema integrity | 25% | 100.0 |
| Failure behaviour | 15% | not applicable |
| Latency | 15% | not applicable |
| Concurrency | 10% | not applicable |
Tool details
- Transport
- remote
- Credential class
- open
- Input schema
- not declared
- Output schema
- not declared
- Side-effect classification
- unclassified
Score history
| Day | Score | Tier | Methodology |
|---|---|---|---|
| 2026-10-06 | 100.0 | shallow | v0.2.0 |
Probe evidence
| Probe | Outcomes |
|---|---|
| schema_integrity | pass: 1 |
Raw request/response logs are not archived yet — the outcome counts above are drawn directly from every recorded trial.
Embed this score
Available for every tool, scored or not — not a verification perk. Always links back to this page.
[](https://vouch.tools/tools/38748706-c508-425e-8306-77547fbf1795)