Calcgrid

Add Hungary Working Days

add_hu_working_days

Read-onlyIdempotent

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

Input Schema

TableJSON Schema

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

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

A4.1/5.0

Behavior5/5

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

Annotations already mark it read-only, idempotent, non-destructive and closed-world, yet the description adds substantial domain behavior: eleven statutory holidays, three paired transfers, three working Saturdays, no automatic substitute Monday, no inferred shift/bank/exchange/payroll schedules, and a decree expiry of 2027-01-01. This is exactly the kind of coverage/limitation context annotations cannot express.

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

Conciseness3/5

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

The definition is long and contains redundancy: the example user requests, the outputs list (already in the output schema), the REST fallback URL and docs link all inflate it. It is information-dense and somewhat front-loaded, but several sentences could be trimmed without loss.

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?

Given a deterministic calculator with a full output schema and complete annotations, the description supplies the calendar coverage, transfer rules and expiry that an agent needs to decide whether the tool applies. Its main gap is the ambiguous when-not sentence; otherwise it is complete enough to invoke correctly.

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

Parameters4/5

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

Schema description coverage is 100%, so the baseline is 3, but the description goes further by spelling out the signed-offset semantics (

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 opening 'Adds or subtracts Hungary authority-scope working days in exact coverage' gives a specific verb and resource, and the tool is clearly the HU member of the country working-day family, distinguishable from check_hu_working_day and count_hu_working_days. The purpose is clear but muddied by the garbled 'Do not use this when hungary 2026 general Monday-Friday work schedule only' clause that interrupts the flow.

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

Usage Guidelines4/5

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

It explicitly says to call the tool directly rather than answering from memory or stopping at discovery, and notes the requirement for an explicit work_schedule. The 'Do not use this when...' sentence appears intended as an exclusion but is syntactically broken, so the when-not guidance is only partially usable.

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?