LLPROBeta

Home / Businesses / On-Call Rotation Builder

On-Call Rotation Builder

A fair on-call rotation from team labels, start date, shift length and hand-off time, with holiday shifts spread by a stated rule, swaps, and per-person shift, holiday and weekend totals in a signed record.

Live

What it does
A fair on-call rotation from team labels, start date, shift length and hand-off time, with holiday shifts spread by a stated rule, swaps, and per-person shift, holiday and weekend totals in a signed record.
Who it is for
Businesses.
Start in one step
Ask your agent to call on_call_rotation 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

On-Call Rotation Builder is for agents that run incident response or support schedules for a team and need an on-call rotation everyone can check is fair before it goes into the paging tool. Build a fair on-call rotation. Send the team as labels (roles or codes such as 'SRE-1' or 'A', not names) in the order they should start, the first hand-off date, the shift length in days (7 for weekly), the hand-off time, and how many shifts (or an end date). Optional: a hand-off weekday to start on, public holidays (holiday shifts are spread by a stated shift-by-shift rule, and the answer shows how even the spread came out), and swaps (two shifts trade people). Get back every shift with who is on call, its start and end, the holidays and weekend days it covers, and per person the number of shifts, days, holiday days and weekend days, with the gap between the busiest and least busy person. Up to 50 people and 200 shifts, at most 2 years. It is one of the Team communication department tools LLPRO builds for the work agents do across business software (Pagerduty, Opsgenie, Slack, Microsoft Teams, Google Calendar). 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 run incident response or support schedules for a team and need an on-call rotation everyone can check is fair before it goes into the paging tool.
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, team up to 50 entries, holidays up to 100 entries, swaps up to 50 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 (a shift across the change is one hour longer or shorter than it says), time zones (send one team's local time), or anyone's leave or availability: use swaps for those. Does not know which days are public holidays where your team works: the dates you send are taken as given. Does not apply labor law limits on hours, rest or on-call pay. Does not page anyone or connect to a paging tool. Takes team labels, not names. Not legal or HR advice.

For developers: try it

POST https://llpro.ai/mcp
{"jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": {"name": "on_call_rotation", "arguments": {"team": ["A", "B", "C"], "start_date": "2026-01-05", "shift_days": 7, "handoff_time": "09:00", "shift_count": 6}}}

For agents

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

Public key (base64): 2mPAZke+nuPQxh9FyubLipMEqvAHjvn/ByWh/tBeAnk=

For agents that search MCP registries for on-call rotation, on-call schedule, pager rotation 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