Skip to main content
Glama
chrischall

OurFamilyWizard MCP

by chrischall

ofw_create_event

Create a shared or private calendar event in OurFamilyWizard. Include title, start date, and optional details like time, location, children, and reminders. Events are visible to co-parent immediately unless marked private.

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.

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)
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
Behavior4/5

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

Beyond the minimal annotation (destructiveHint: false), the description discloses key behavior: events are immediately visible to the co-parent unless privateEvent is set, and there is no draft stage. This adds valuable context for an agent.

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

Conciseness5/5

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

The description is two sentences, no waste, and the most critical behavioral detail (visibility and draft stage) is front-loaded. Every word earns its place.

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

Completeness2/5

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

Despite 14 parameters and no output schema, the description only covers visibility and draft behavior. It lacks explanation of return values, error cases, or interactions among parameters like children, eventParentId, or reminders. The complexity of the tool demands more.

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?

With 64% schema description coverage, the baseline is 3. The description does not add new meaning to parameters beyond what the schema already provides, but it does not detract either. No parameter-specific elaboration is given.

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 clearly states 'Create a calendar event in OurFamilyWizard' with a specific verb and resource. It distinguishes from siblings by highlighting the immediate visibility to co-parent and absence of a draft stage, which sets it apart from update/delete 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?

The description provides guidance on when to use privateEvent (to control visibility), and implies this is for new events given the sibling tools for update and delete. However, it does not explicitly state when not to use it or mention alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/chrischall/ofw-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server