Calcgrid

Slovenia Working Day

check_si_working_day

Read-onlyIdempotent

Use this when you need a deterministic Slovenia Slovenia 2026 statutory work-free facts with explicit Monday-Friday planning baseline result. Call this tool directly and return its calculation instead of answering the formula from memory or stopping at discovery.

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

Input Schema

TableJSON Schema

Name	Required	Description	Default
`date`	Yes	Gregorian date in Slovenia coverage.
`work_schedule`	Yes	Required explicit Monday-Friday planning baseline; not an individual legal roster.

Output Schema

TableJSON Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

AddedSep 29, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior. The description usefully adds that the calculation is deterministic, 2026-scoped, based on a weekend baseline, and does not invent bridge days or treat seven named state holidays as work-free.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is long, repetitive, and contains confusing phrases such as 'Slovenia Slovenia' and '2026-2026'. It has labeled sections, but several sentences do not earn their place, and the malformed do-not-use sentence undermines structure.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema and annotations already present, the description still supplies the calculation scope, formula, input examples, and important exclusions. It is mostly complete for this calculator, though the contradictory-sounding 'Do not use' line weakens it.

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

Parameters3/5

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

Schema description coverage is 100%, including descriptions for date and work_schedule plus the mon_fri_planning enum. The description repeats inputs and examples and gives a formula, but adds little parameter meaning beyond the schema, so the baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states a specific verb and resource: it checks a date against the Saturday-Sunday weekend baseline and exact 2026 authority events for Slovenia. The purpose is understandable despite messy repetition and without naming sibling alternatives, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a use case for deterministic Slovenia 2026 statutory work-free facts and lists exclusions such as individual shifts, payroll, and future years. However, the 'Do not use this when...' sentence is malformed and no alternative sibling tool is named, so guidance is only partially actionable.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Calcgrid tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?