LLPROBeta

Home / Businesses / Retention Schedule Destroy-By Dates

Retention Schedule Destroy-By Dates

Work out the keep-through and earliest destruction date for each record class from creation dates and the retention years your own schedule sends, with a signed record.

Testing

What it does
Work out the keep-through and earliest destruction date for each record class from creation dates and the retention years your own schedule sends, with a signed record.
Who it is for
Businesses.
Start in one step
Ask your agent to call retention_schedule_dates 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

Retention Schedule Destroy-By Dates is for agents that clean up or archive a business's files and need, class by class, the exact date a record may be destroyed under the company's own retention schedule. Work out, for each record class in a company's own retention schedule, the date it must be kept through and the first day it may be destroyed. Send each class with its creation date and the retention years (and months) the schedule says, and optionally a date to check against (as_of), whether the count starts at the creation date, the end of that month or the end of that year, and whether the class is permanent or on legal hold. Get back, for every class, the keep-through date, the earliest destruction date and, if you sent as_of, whether it is still to be kept, eligible for destruction, on hold or permanent, with the days left. The retention years are yours: the tool does not know what the law requires. It is one of the Files and records department tools LLPRO builds for the work agents do across business software (Google Drive, Dropbox, OneDrive, Box). 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 clean up or archive a business's files and need, class by class, the exact date a record may be destroyed under the company's own retention schedule.
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, records up to 200 entries; larger requests are refused, never cut. Unknown fields are refused with the list of accepted ones. Nothing you send is stored by the tool; no model and no network are used. Does not know how long any record must legally be kept: the years come from the caller's own retention schedule, which a lawyer or records manager sets (the periods differ by law, state, industry and record type). Does not check for holds, audits, litigation or open disputes beyond the legal_hold flag the caller sends, does not decide that destruction is allowed, and does not delete or look at any record. Counts calendar dates only (no business days, no time zones, fiscal years or event-based triggers such as 'after the contract ends': send that end date as the creation date). Not legal advice.

For developers: try it

POST https://llpro.ai/mcp
{"jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": {"name": "retention_schedule_dates", "arguments": {"records": [{"record_class": "vendor contracts", "created": "2020-03-15", "retention_years": 7}], "as_of": "2026-11-22"}}}

For agents

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

Public key (base64): pAlGfJ8wccaqZsyrew04ZojOPjS7IGLjpJcD+OZkN0Y=

For agents that search MCP registries for retention schedule, records retention, destroy by date 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