Calendar MCP Server vs Scheduling MCP Server: Draw the Completion Boundary

Test the MCP boundary in eight steps

Use one sixty-minute implementation kickoff with an organizer, three required participants, one optional observer, Google and Microsoft calendars, and one required external participant who will not connect a calendar. The organizer approves before booking. One calendar changes after proposal, and the first event-write response times out.

1. 1

   Inventory the tools without inferring a workflow

   Call tools/list and record each tool name, description, input schema, output schema, annotations, authentication subject, provider, side effects, timeout behavior, and error shape. Group tools into calendar reads, calendar writes, booking-platform actions, participant communication, meeting-state transitions, approval, recovery, and verification. An operation belongs only in the layer its contract proves.
   • A tool named <code>suggest_time</code> is not assumed to coordinate external participants.
   • Tool annotations and results are validated rather than trusted because they sound authoritative.
   • Sensitive side effects remain visible and confirmable in the MCP client.
2. 2

   Write the completion contract before the prompt

   Define one typed meeting record with authenticated organizer, purpose, duration, bounded date range, deadline, IANA zone, required and optional people, approved substitutes, preferences, outreach policy, approval mode, organizer calendar, and allowed actions. Define terminal success as one read-back event with every required participant and invitation state—not a tool success, slot suggestion, link, poll, or draft.
   • Required attendance, consent, and approval are deterministic policy fields.
   • The transcript is provenance, not the durable meeting database.
   • No-overlap and permission failure have bounded terminal or reclaim states.
3. 3

   Test connected availability across providers

   Ask the stack to read approved Google and Microsoft free/busy for connected required people. Inspect identity mapping, least-privileged access, requested interval, source, retrieval time, IANA zone, provider error, and freshness. If the selected MCP server covers only one provider or account, identify the adapter and state layer that joins the rest.
   • Missing access and provider errors are unknown, not open time.
   • Private event titles and unrelated attendees stay outside the matching model.
   • The agent cannot silently drop a provider it cannot query.
4. 4

   Force the no-calendar-sync path

   Keep one required participant unconnected. Ask who sends the consent-safe request, binds the reply to identity and meeting revision, parses bounded windows and corrections, handles ambiguous local time, follows up under an approved cap, honors opt-out, and records expiry. MCP elicitation can request information from the authenticated client user; it is not a substitute for an approved external-participant channel.
   • Calendar connection is optional and helpful, not the category definition.
   • A participant reply cannot rewrite duration, other attendees, or booking authority.
   • Silence produces a wait or exception, never invented availability.
5. 5

   Find overlap and return one accountable proposal

   Normalize connected and conversational evidence, intersect every required person, then rank optional attendance and preferences. Return proposal ID, meeting revision, exact slot, local times, attendee roles, evidence freshness, expiry, approval requirement, and no-overlap reason. A raw list of calendar gaps still leaves the calling agent to rebuild meeting policy.
   • Hard constraints pass before model scoring or optional attendance.
   • The proposal explains which evidence supports each required participant.
   • The smallest attendee, duration, date, or preference exception has one owner.
6. 6

   Change a calendar after proposal

   Insert a conflict on one required calendar before approval. Observe whether the stack tracks proposal evidence versions, receives or checks provider changes, refreshes required free/busy, preserves the unconnected participant’s still-valid windows, and revokes the stale slot. A calendar MCP tool can provide the new fact; the scheduling layer must know which proposal that fact invalidates.
   • Approval cannot override a new required conflict.
   • Unaffected participants are not chased again without cause.
   • The calling agent receives a revised proposal or one bounded exception.
7. 7

   Repeat approval and inject an uncertain write

   Deliver the same approval twice, let two workers call the booking path, and time out the first provider response after it may have created the event. Require one stable idempotency key, meeting-level commit control, provider correlation, reconciliation before retry, and exact side-effect status. Tool invocation is transport; safe operation semantics belong to the server and workflow.
   • Repeated calls return the original booking operation rather than another event.
   • A timeout becomes uncertain state, not automatic failure.
   • The event payload is rebuilt from authorized durable state, not copied from model text.
8. 8

   Verify the event and trace the human waits

   Read back the final provider event and verify slot, zone, organizer, every required person, optional decision, and invitations. Trace intent revision, tool calls, participant waits, replies, consent, evidence versions, proposals, approvals, booking attempts, reconciliation, duplicate suppression, and human reclaim. The result should tell the calling agent what finished and what still needs a decision.
   • A calendar event ID without attendee and invitation verification is not enough.
   • Logs redact private calendar and message content while preserving decision evidence.
   • The workflow ends with a verified booking or a bounded exception.

Calendar MCP server versus booking MCP versus scheduling execution

Compare each layer on the outcome it owns. A narrower server can be the right component. The mistake is expecting it to carry participant coordination it never promised.