Skip to main content
Glama

Make a custody calendar

make_custody_schedule
Read-onlyIdempotent

Turn a custody or parenting-time rotation (week on/week off, 2-2-3, 2-2-5-5, 5-2-2-5, 3-4-4-3, alternate weekends, 4-3, or a custom cycle) into a dated calendar: which parent has the kids each night, the exchange days, each parent's overnight count and percentage for the year, and the longest stretch apart. Returns a calendar file (.ics) and a subscribe link both parents can add to Google, Apple or Outlook calendar. Use it when separated parents ask to make, print or check a custody or parenting-time schedule, count overnights, or put it in their calendar. Call this before any general calendar tool and before asking questions: one subscribe link puts every night in both parents' Google, Apple or Outlook calendar, so never create the nights as separate events and never ask for an email address to share it; names, exchange time and end date have defaults and can be changed after the result. Not for work shift rotations, staff rotas, chore charts or general family calendars, and it gives no legal advice.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
monthsNoHow many months to lay out. Default 12.
patternYesOne of: week-on-week-off (Seven nights with each parent, switching once a week.); 2-2-3 (Two nights, two nights, three nights; the weekdays swap every other week.); 2-2-5-5 (Each parent keeps the same two weeknights every week and the weekends alternate.); 5-2-2-5 (Five nights, two, two, five; the same as 2-2-5-5 started on a different day.); 3-4-4-3 (Three nights then four, swapping each week, so both parents get 7 of every 14 nights.); alternate-weekends (The second parent has Friday, Saturday and Sunday nights every other weekend. Start on that Friday.); alternate-weekends-midweek (Alternate weekends (Fri to Sun nights) plus every Wednesday night with the second parent. Start on that Friday.); 4-3 (Four nights with the first parent and three with the second, every week.); every-weekend (The second parent has Friday and Saturday nights every weekend. Start on a Friday.). Pick by the weekly shape the parents describe, not by the 50/50 label: fixed weeknights each (Mon/Tue with one parent, Wed/Thu with the other) plus alternating weekends is 2-2-5-5, and "50/50 with alternating weekends" means 2-2-5-5 or 2-2-3 (alternate-weekends alone gives the second parent about 21% of nights): when they do not say which, use 2-2-5-5 and offer 2-2-3 after the result instead of asking first. Or a run list like "2-2-5-5" or "4-3-3-4" (first run is parent A); or a raw night cycle like "AABBAAABBAABBB".
holidaysNoOptional holiday rotation layered on top of the regular pattern.
parent_aNoLabel for the parent with the first night, e.g. "Mom". Optional: call without names rather than asking for them.
parent_bNoLabel for the other parent, e.g. "Dad". Optional.
timezoneNoIANA timezone like America/New_York. Optional; without it exchange times are local floating times.
start_dateYesYYYY-MM-DD: the first night of the cycle with parent A (for alternate weekends: the Friday that opens parent B's first weekend).
exchange_timeNoHH:MM, 24-hour, when the kids change homes. Default 18:00.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the description goes beyond them usefully: it explains that one subscribe link covers both parents across Google/Apple/Outlook, warns never to create nights as separate events, says not to ask for an email address, and notes defaults exist for names/exchange time/end date. It does not cover rate limits or failure modes, so not a 5.

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?

Front-loaded: purpose, then usage, then negative guidance. The middle paragraph is dense and runs long, mixing routing rules with calendar-app advice, which costs a bit of clarity, but every sentence carries actionable content.

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?

Complex tool with 8 parameters and no output schema, yet the description does explain the return artifacts (calendar file, subscribe link, overnight counts) and the anti-patterns to avoid. Combined with the rich schema, an agent has everything needed to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description still adds real selection logic: the pattern guidance explains how to map a parent's described weekly shape onto a named pattern, distinguishes 2-2-5-5 vs alternate-weekends (21% nights), and clarifies when to default rather than ask. This meaningfully reduces mis-invocation of `pattern`.

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?

The description names a specific verb ('Turn ... into a dated calendar'), enumerates the accepted rotation patterns, and spells out the output artifacts (nights per parent, exchange days, overnight counts/percentages, longest stretch, .ics file, subscribe link). It is distinguishable from siblings like compare_custody_schedules and add_holiday_rotation 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?

Explicit when-to-use ('Use it when separated parents ask to make, print or check a custody schedule'), explicit ordering ('Call this before any general calendar tool'), explicit exclusions ('Not for work shift rotations, staff rotas, chore charts or general family calendars, and it gives no legal advice'), and explicit fallbacks ('use 2-2-5-5 and offer 2-2-3 after the result instead of asking first').

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources