OurFamilyWizard MCP

ofw_create_event

Destructive

Create a shared or private calendar event in OurFamilyWizard for co-parenting schedules. Confirms shared events before saving and requires explicit approval.

Instructions

Create a calendar event in OurFamilyWizard. Unless privateEvent is true, the event is immediately visible to the co-parent — there is no draft stage — so a shared event is confirmed first (a private one is not). If the request fails without a definitive answer the result is EVENT_UNCONFIRMED: the event may already exist, so do NOT retry until ofw_list_events shows it did not land. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call performs NO write and returns a preview of exactly what would happen plus a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE).

Input Schema

Name	Required	Description
`notes`	No
`title`	Yes
`allDay`	No
`endDate`	No	End date YYYY-MM-DD (default: startDate)
`endTime`	No	End time HH:mm, 24-hour (required unless allDay)
`children`	No	Child userIds to tag (see ofw_get_profile)
`location`	No
`startDate`	Yes	Start date YYYY-MM-DD
`startTime`	No	Start time HH:mm, 24-hour (required unless allDay)
`confirmToken`	No	ONLY for the two-step confirmation fallback (a client without MCP elicitation). The confirmToken from this same tool's phase-1 "confirmation-required" response, passed back ONLY after the user has seen that preview and explicitly approved it in chat — never on the first call, never invented, never reused. Call again with the same arguments. Ignored when the client supports elicitation.
`privateEvent`	No	true = visible only to you; default false = shared with co-parent
`eventParentId`	No	userId of the parent the event is 'for'
`pickUpParentId`	No	userId of the pick-up parent
`dropOffParentId`	No	userId of the drop-off parent
`reminderMinutes`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv2.19.4Sep 25, 2026

addedInput schema / properties / confirmToken

Added value: +{
+  "description": "ONLY for the two-step confirmation fallback (a client without MCP elicitation). The confirmToken from this same tool's phase-1 \"confirmation-required\" response, passed back ONLY after the user has seen that preview and explicitly approved it in chat — never on the first call, never invented, never reused. Call again with the same arguments. Ignored when the client supports elicitation.",
+  "type": "string"
+}

Changed1 schema field changedv2.17.0Sep 17, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

First observedv2.8.0Jul 28, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Goes well beyond the readOnly/destructive/openWorld annotations by disclosing the confirmation protocol, the two-step confirmToken fallback, the immediate visibility of shared events, and the ambiguous EVENT_UNCONFIRMED failure mode with its retry prohibition. This is precisely the kind of safety-critical behavior an agent needs and cannot get from structured fields.

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?

Purpose is front-loaded in the first clause, and each sentence carries non-redundant operational detail. It is dense and somewhat run-on in the confirmation/fallback sentence, but there is little waste.

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

Completeness4/5

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

For a complex mutating tool with 15 params and no output schema, the description covers the crucial gaps: confirmation, idempotency/retry safety, and visibility semantics. It leaves some parameters (notes, location, reminderMinutes) unexplained, but the higher-risk behavior is addressed.

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

Parameters3/5

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

Schema description coverage is 67%, covering endDate, times, children, confirmToken, privateEvent, and the parent IDs, so most semantics live in the schema. The description adds meaning for privateEvent's visibility consequence and confirmToken's usage constraints but does not compensate for the undocumented params (notes, title, allDay, location, reminderMinutes). Baseline 3 is appropriate.

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 and resource ('Create a calendar event in OurFamilyWizard') and implicitly contrasts with siblings like ofw_update_event/ofw_delete_event/ofw_list_events by naming ofw_list_events as the verification path. An agent knows exactly what this tool does and how it relates to the other event tools.

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

Usage Guidelines4/5

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

Gives strong conditional guidance: shared vs private visibility, no draft stage, do NOT retry on EVENT_UNCONFIRMED until ofw_list_events confirms absence, and the confirmation flow. It names one alternative (ofw_list_events) but does not explicitly route to ofw_update_event/ofw_delete_event for other operations, so it stops short of full when/when-not/alternatives coverage.

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

ofw_create_event

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools