mcp-tools

Recurring schedule

recurring_schedule

Read-onlyIdempotent

Prepare weekly, biweekly, or monthly task calendars and estimate monthly effort for up to 20 tasks, returning hours, recurrence rules, and an RFC 5545 calendar.

Instructions

Prepare weekly, biweekly or monthly task calendars and estimate monthly effort for up to 20 tasks. Use to draft a recurring work plan; use cron_next_runs to preview existing cron syntax or meeting_time_zones for shared workday slots. Returns monthly hours, first dates, recurrence rules and an RFC 5545 calendar. Times float in the importing calendar’s local zone; weekly estimates use 52/12 runs per month and biweekly 26/12. owner is a planning label, with no assignment or execution. No calendar is updated; an empty task list returns zero hours and no events.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`tasks`	Yes	Tasks to include in the estimate and calendar. [] returns zero hours and a calendar with no events.
`startDate`	Yes	Earliest date for the first occurrence of each task, from 2000-01-01 to 2100-12-31.

Output Schema

TableJSON Schema

Name	Required	Description
`ics`	Yes	RFC 5545 calendar with CRLF folding and floating local times.
`tool`	Yes	Calculator identifier for this result.
`input`	Yes	Normalized inputs used for this calculation.
`units`	Yes	Units for the numeric and time fields in this result.
`method`	Yes	Calculation or ranking method applied to the inputs.
`schedules`	Yes	Normalized tasks with their first occurrence and recurrence rule, in input order.
`provenance`	Yes	Dated data sources or runtime time-zone information used for this result.
`assumptions`	Yes	Limits and assumptions to retain when presenting the result.
`monthlyHours`	Yes	Estimated monthly hours using 52/12 weekly, 26/12 biweekly and one monthly run.

Schema Changelog

Changes observed during successful MCP inspections.

Changed65 schema fields changedv1.1.0Oct 3, 2026
- changedInput schema / properties / startDate / description
```
Previous value: -"Real date from 2000-01-01 to 2100-12-31."New value: +"Earliest date for the first occurrence of each task, from 2000-01-01 to 2100-12-31."
```
- addedInput schema / properties / startDate / examples
```
Added value: +[
+  "2026-10-05"
+]
```
- addedInput schema / properties / startDate / maxLength
```
Added value: +10
```
- addedInput schema / properties / startDate / minLength
```
Added value: +10
```
- addedInput schema / properties / tasks / description
```
Added value: +"Tasks to include in the estimate and calendar. [] returns zero hours and a calendar with no events."
```
- addedInput schema / properties / tasks / items / properties / day / description
```
Added value: +"Weekday for weekly/biweekly tasks. Required but ignored for monthly tasks."
```
- addedInput schema / properties / tasks / items / properties / day / examples
```
Added value: +[
+  "MO"
+]
```
- addedInput schema / properties / tasks / items / properties / frequency / description
```
Added value: +"Repeat every week, every two weeks from the first matching weekday, or every month."
```
- addedInput schema / properties / tasks / items / properties / minutes / description
```
Added value: +"Estimated minutes per run; used for event duration and monthly hours."
```
- addedInput schema / properties / tasks / items / properties / minutes / examples
```
Added value: +[
+  35
+]
```
- addedInput schema / properties / tasks / items / properties / monthday / description
```
Added value: +"Day of month for monthly tasks, limited to dates present in every month. Required but ignored for weekly/biweekly tasks."
```
- addedInput schema / properties / tasks / items / properties / monthday / examples
```
Added value: +[
+  1
+]
```
- addedInput schema / properties / tasks / items / properties / owner / description
```
Added value: +"Planning label: delegate to an operator, keep for yourself, or decide later. Included in the calendar note; does not assign or execute work."
```
- addedInput schema / properties / tasks / items / properties / time / description
```
Added value: +"24-hour HH:mm start time, floating in the importing calendar’s local time zone."
```
- addedInput schema / properties / tasks / items / properties / time / examples
```
Added value: +[
+  "09:00"
+]
```
- addedInput schema / properties / tasks / items / properties / time / maxLength
```
Added value: +5
```
- addedInput schema / properties / tasks / items / properties / time / minLength
```
Added value: +5
```
- addedInput schema / properties / tasks / items / properties / title / description
```
Added value: +"Task label used as the calendar event summary."
```
- addedInput schema / properties / tasks / items / properties / title / examples
```
Added value: +[
+  "Investor update"
+]
```
- addedOutput schema / description
```
Added value: +"Monthly effort estimate, normalized recurrence rules and an importable floating-time calendar."
```
- addedOutput schema / properties / assumptions / description
```
Added value: +"Limits and assumptions to retain when presenting the result."
```
- addedOutput schema / properties / input / description
```
Added value: +"Normalized inputs used for this calculation."
```
- changedOutput schema / properties / input / properties / startDate / description
```
Previous value: -"Real date from 2000-01-01 to 2100-12-31."New value: +"Earliest date for the first occurrence of each task, from 2000-01-01 to 2100-12-31."
```
- addedOutput schema / properties / input / properties / startDate / examples
```
Added value: +[
+  "2026-10-05"
+]
```
- addedOutput schema / properties / input / properties / startDate / maxLength
```
Added value: +10
```
- addedOutput schema / properties / input / properties / startDate / minLength
```
Added value: +10
```
- addedOutput schema / properties / input / properties / tasks / description
```
Added value: +"Tasks to include in the estimate and calendar. [] returns zero hours and a calendar with no events."
```
- addedOutput schema / properties / input / properties / tasks / items / properties / day / description
```
Added value: +"Weekday for weekly/biweekly tasks. Required but ignored for monthly tasks."
```
- addedOutput schema / properties / input / properties / tasks / items / properties / day / examples
```
Added value: +[
+  "MO"
+]
```
- addedOutput schema / properties / input / properties / tasks / items / properties / frequency / description
```
Added value: +"Repeat every week, every two weeks from the first matching weekday, or every month."
```
- addedOutput schema / properties / input / properties / tasks / items / properties / minutes / description
```
Added value: +"Estimated minutes per run; used for event duration and monthly hours."
```
- addedOutput schema / properties / input / properties / tasks / items / properties / minutes / examples
```
Added value: +[
+  35
+]
```
- addedOutput schema / properties / input / properties / tasks / items / properties / monthday / description
```
Added value: +"Day of month for monthly tasks, limited to dates present in every month. Required but ignored for weekly/biweekly tasks."
```
- addedOutput schema / properties / input / properties / tasks / items / properties / monthday / examples
```
Added value: +[
+  1
+]
```
- addedOutput schema / properties / input / properties / tasks / items / properties / owner / description
```
Added value: +"Planning label: delegate to an operator, keep for yourself, or decide later. Included in the calendar note; does not assign or execute work."
```
- addedOutput schema / properties / input / properties / tasks / items / properties / time / description
```
Added value: +"24-hour HH:mm start time, floating in the importing calendar’s local time zone."
```
- addedOutput schema / properties / input / properties / tasks / items / properties / time / examples
```
Added value: +[
+  "09:00"
+]
```
- addedOutput schema / properties / input / properties / tasks / items / properties / time / maxLength
```
Added value: +5
```
- addedOutput schema / properties / input / properties / tasks / items / properties / time / minLength
```
Added value: +5
```
- addedOutput schema / properties / input / properties / tasks / items / properties / title / description
```
Added value: +"Task label used as the calendar event summary."
```
- addedOutput schema / properties / input / properties / tasks / items / properties / title / examples
```
Added value: +[
+  "Investor update"
+]
```
- addedOutput schema / properties / method / description
```
Added value: +"Calculation or ranking method applied to the inputs."
```
- addedOutput schema / properties / monthlyHours / description
```
Added value: +"Estimated monthly hours using 52/12 weekly, 26/12 biweekly and one monthly run."
```
- addedOutput schema / properties / provenance / additionalProperties / description
```
Added value: +"Unit or source detail for the named field."
```
- addedOutput schema / properties / provenance / description
```
Added value: +"Dated data sources or runtime time-zone information used for this result."
```
- addedOutput schema / properties / schedules / description
```
Added value: +"Normalized tasks with their first occurrence and recurrence rule, in input order."
```
- addedOutput schema / properties / schedules / items / properties / day / description
```
Added value: +"Weekday for weekly/biweekly tasks. Required but ignored for monthly tasks."
```
- addedOutput schema / properties / schedules / items / properties / day / examples
```
Added value: +[
+  "MO"
+]
```
- addedOutput schema / properties / schedules / items / properties / firstDate / description
```
Added value: +"First occurrence on or after startDate."
```
- addedOutput schema / properties / schedules / items / properties / frequency / description
```
Added value: +"Repeat every week, every two weeks from the first matching weekday, or every month."
```
- addedOutput schema / properties / schedules / items / properties / minutes / description
```
Added value: +"Estimated minutes per run; used for event duration and monthly hours."
```
- addedOutput schema / properties / schedules / items / properties / minutes / examples
```
Added value: +[
+  35
+]
```
- addedOutput schema / properties / schedules / items / properties / monthday / description
```
Added value: +"Day of month for monthly tasks, limited to dates present in every month. Required but ignored for weekly/biweekly tasks."
```
- addedOutput schema / properties / schedules / items / properties / monthday / examples
```
Added value: +[
+  1
+]
```
- addedOutput schema / properties / schedules / items / properties / owner / description
```
Added value: +"Planning label: delegate to an operator, keep for yourself, or decide later. Included in the calendar note; does not assign or execute work."
```
- addedOutput schema / properties / schedules / items / properties / recurrenceRule / description
```
Added value: +"RFC 5545 RRULE matching the task frequency and day."
```
- addedOutput schema / properties / schedules / items / properties / time / description
```
Added value: +"24-hour HH:mm start time, floating in the importing calendar’s local time zone."
```
- addedOutput schema / properties / schedules / items / properties / time / examples
```
Added value: +[
+  "09:00"
+]
```
- addedOutput schema / properties / schedules / items / properties / time / maxLength
```
Added value: +5
```
- addedOutput schema / properties / schedules / items / properties / time / minLength
```
Added value: +5
```
- addedOutput schema / properties / schedules / items / properties / title / description
```
Added value: +"Task label used as the calendar event summary."
```
- addedOutput schema / properties / schedules / items / properties / title / examples
```
Added value: +[
+  "Investor update"
+]
```
- addedOutput schema / properties / tool / description
```
Added value: +"Calculator identifier for this result."
```
- addedOutput schema / properties / units / additionalProperties / description
```
Added value: +"Unit or source detail for the named field."
```
- addedOutput schema / properties / units / description
```
Added value: +"Units for the numeric and time fields in this result."
```
First observedv1.0.0Oct 2, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, but the description goes further: 'No calendar is updated', empty task list yields zero hours and no events, times float in the importing calendar's local zone, and owner is only a planning label with no assignment or execution. It also discloses the estimation math (52/12 weekly, 26/12 biweekly), which no annotation or schema field conveys.

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

Conciseness4/5

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

Five tight sentences, front-loaded with the primary action and scope before alternatives and caveats; every sentence carries distinct information (alternatives, return shape, time semantics, estimation math, no-side-effect guarantee). Dense but not padded, though the return-value sentence overlaps with the output schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 2-parameter tool with full schema coverage and an output schema, this covers everything an agent needs: what it produces, how effort is estimated, time-zone behavior, side-effect absence, and the empty-input edge case. Nothing material is missing.

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 coverage is 100%, so the baseline is 3 and the schema already documents day/monthday/time/owner semantics. The description still adds value the schema does not: the 52/12 and 26/12 runs-per-month estimation formula and the floating-time-zone interpretation of the produced times, which is what an agent needs to predict output. Slightly above baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Prepare... estimate') and resource ('weekly, biweekly or monthly task calendars'), plus the scope bound of 20 tasks. It names siblings cron_next_runs and meeting_time_zones so the agent can separate this planning tool from the cron-preview and timezone tools without opening a schema.

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

Usage Guidelines5/5

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

Explicitly says to use it 'to draft a recurring work plan' and routes to alternatives by condition: cron_next_runs for existing cron syntax, meeting_time_zones for shared workday slots. When-to-use and which-alternative are both stated, not inferred.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server