LLPROBeta

Home / Businesses / Working Days and Hours in a Year or Month

Working Days and Hours in a Year or Month

Count the working days and working hours in a year or one month, skipping weekends and the holidays you list, with the holidays that changed nothing named and a signed record.

Testing

What it does
Count the working days and working hours in a year or one month, skipping weekends and the holidays you list, with the holidays that changed nothing named and a signed record.
Who it is for
Businesses.
Start in one step
Ask your agent to call workday_hours_year at llpro.ai/mcp (free, no sign-up). This page explains the tool; it has no form to run it.
What to expect
Testing: open to try. Free

New to this? Start here.

What it does

Working Days and Hours in a Year or Month is for agents that plan staffing, set hourly rates from a salary or budget a work year for a business and need the days and hours counted the same way every time. Count the working days and working hours in a calendar year or in one month of it. Weekends (Saturday and Sunday) are skipped, and so are the holidays you list that fall on a weekday. Send the year, optionally a month, the hours in a working day (default 8) and your holiday dates. Get back the weekdays, the holidays taken off, the working days, the working hours and the holidays that did not change the count (weekend, repeated or in another month). It is one of the HR and payroll department tools LLPRO builds for the work agents do across business software (Gusto, ADP, Paychex, Quickbooks Payroll, Rippling). Every answer carries the written rule it used, what it does not do, its sources with dates, and an Ed25519 signature you can check against the key below.

Who it is for
Agents that plan staffing, set hourly rates from a salary or budget a work year for a business and need the days and hours counted the same way every time.
Price
Free, no sign-up: 120 calls an hour per address and 3,000 an hour across all callers. Paid calls are planned and not charging.
Limits
Up to 30,000 bytes per call, holidays up to 60 entries; larger requests are refused, never cut. Unknown fields are refused with the list of accepted ones. Money takes up to 2 decimals unless a field says more, and every sum is exact (send amounts as numbers or strings; commas only as thousands separators, 1,234.56). Nothing you send is stored by the tool; no model and no network are used. Does not know any holiday: it takes off only the dates you send, and does not move a holiday that lands on a weekend to a weekday (send the weekday you observe). Does not give the 2,087-hour federal pay divisor (which divides a 52.1429-week year, holidays and leave included) or any pay figure; does not subtract leave, sick days or half days; does not handle a work week other than Monday to Friday. Not legal, tax or payroll advice.

For developers: try it

POST https://llpro.ai/mcp
{"jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": {"name": "workday_hours_year", "arguments": {"year": 2026}}}

For agents

Tool workday_hours_year on https://llpro.ai/mcp and in the tools list. Signed answers are checked with the public key below (signer llpro1:w4c5jgnp5ilp52nmcgds3vseeq): an Ed25519 signature over the observation as canonical JSON (sorted keys, no spaces).

Public key (base64): adqv79/Y7M8pYl+cniH1T5pecwYpcjgqeEjnrSTsvt8=

For agents that search MCP registries for working hours in a year, working days in a year, workdays tools (listed in MCP registries, served by the LLPRO gateway: MCP, agent-to-agent and REST). One fixed, written rule per call, a signed record, no account needed.

Next

For agents: this page as Markdown · JSON · llms.txt · MCP endpoint llpro.ai/mcp · agent card