LLPROBeta

Home / Businesses / Shift Coverage Check

Shift Coverage Check

Compare a staff schedule with the staff you need, minute by minute: every gap hour and overstaffed hour, the exact short periods, staff-hour totals and the covered share, signed.

Testing

What it does
Compare a staff schedule with the staff you need, minute by minute: every gap hour and overstaffed hour, the exact short periods, staff-hour totals and the covered share, signed.
Who it is for
Businesses.
Start in one step
Ask your agent to call shift_coverage 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

Shift Coverage Check is for agents that build or check staff schedules for a business (stores, clinics, call centers, restaurants, warehouses) and need the gaps and the overstaffing found before the schedule is posted. Check a staff schedule against the staff you need. Send the scheduled shifts (date, start, end and how many people work it) and the required staff per time window (date, start, end, head count); overnight shifts and windows are fine. Get back, hour by hour, every gap hour (fewer people on duty than required at any minute of the hour, with how many short and for how many staff-minutes), every overstaffed hour (more people than required for the whole hour), the exact short periods to the minute, and totals: staff-hours required, scheduled, short and over, and the share of required staff-minutes that are covered. Up to 200 shifts and 200 windows over at most 8 days. Shifts carry a head count only: send no names. It is one of the Scheduling department tools LLPRO builds for the work agents do across business software (Google Calendar, Outlook, When I Work, Deputy, Homebase). 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 build or check staff schedules for a business (stores, clinics, call centers, restaurants, warehouses) and need the gaps and the overstaffing found before the schedule is posted.
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, shifts up to 200 entries, need up to 200 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 adjust for daylight-saving clock changes (the night clocks move has one hour more or less than the times say), breaks inside a shift (split the shift), skills, roles or locations (send one role per call), labor law limits on hours, rest or overtime, or who should fill a gap. Does not forecast demand: the required staff you send are taken as given. Takes no names or employee IDs. Not legal advice.

For developers: try it

POST https://llpro.ai/mcp
{"jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": {"name": "shift_coverage", "arguments": {"shifts": [{"date": "2026-11-16", "start": "09:00", "end": "17:00"}, {"date": "2026-11-16", "start": "09:00", "end": "13:00"}, {"date": "2026-11-16", "start": "13:00", "end": "17:00"}], "need": [{"date": "2026-11-16", "start": "09:00", "end": "17:00", "staff": 2}]}}}

For agents

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

Public key (base64): Pq1qdaeG5qWNqUg7/cI1pQ4AuGN5G0QpSR4dAWfe1LM=

For agents that search MCP registries for shift coverage, staff scheduling, understaffed hours tools (listed in MCP registries, served by the Campus 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