Skip to main content
Glama
chrischall

ofw-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

ofw_create_event

Create a calendar event in OurFamilyWizard, with confirmation to avoid duplicates. Shared events are visible to co-parent immediately; private events are visible only to you.

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

TableJSON Schema
NameRequiredDescriptionDefault
notesNo
titleYes
allDayNo
endDateNoEnd date YYYY-MM-DD (default: startDate)
endTimeNoEnd time HH:mm, 24-hour (required unless allDay)
childrenNoChild userIds to tag (see ofw_get_profile)
locationNo
startDateYesStart date YYYY-MM-DD
startTimeNoStart time HH:mm, 24-hour (required unless allDay)
confirmTokenNoONLY 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.
privateEventNotrue = visible only to you; default false = shared with co-parent
eventParentIdNouserId of the parent the event is 'for'
pickUpParentIdNouserId of the pick-up parent
dropOffParentIdNouserId of the drop-off parent
reminderMinutesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.19.4

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, openWorldHint=true, destructiveHint=false), the description discloses the no-draft publication behavior, the confirmation requirement, the two-step fallback with confirmToken, and the 'may already exist' uncertainty. This significantly extends what the annotations alone convey.

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?

The description is dense but every clause carries operational value: confirmation, visibility, failure ambiguity, and retry prohibition. It is somewhat long and could be split into shorter sentences, but none of the content is filler.

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 15-parameter write tool with no output schema, the description covers the non-obvious execution model thoroughly: preview-first behavior, confirmToken reuse rule, and the EVENT_UNCONFIRMED edge case. Required/optional fields are left to the schema, which is appropriate.

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?

With 67% schema coverage, the schema already handles most parameters. The description adds behavioral meaning for privateEvent (visibility to co-parent) and confirmToken (fallback-only, never first call), which are the parameters most likely to be misinterpreted by an agent.

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 opens with a specific action and resource: 'Create a calendar event in OurFamilyWizard.' It immediately distinguishes itself from update/delete/list siblings by its create semantics and further clarifies the sharing model with co-parent visibility.

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?

The description gives strong situational guidance: shared events need confirmation, private events do not, and on an EVENT_UNCONFIRMED failure the agent must check ofw_list_events before retrying. It does not, however, explicitly contrast this tool with ofw_update_event or state when update should be preferred.

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

Deploy Server

Other Tools