Skip to main content
Glama
chrischall

OurFamilyWizard MCP

by chrischall

ofw_sync_messages

Syncs OurFamilyWizard messages into a local cache, returning folder counts and unread inbox message IDs (without marking them read). Supports resumable deep backfill for history gaps.

Instructions

Sync messages from OurFamilyWizard into the local cache. Returns counts per folder and a list of unread inbox messages whose bodies were NOT fetched (to avoid mark-as-read on OFW). Call ofw_get_message(id) on those to read them. EVERY call re-checks the newest page first, so new messages are picked up promptly even while an old-history backfill is still running; only then does it spend what is left of its budget advancing that backfill. Pass deep:true to walk all OFW pages instead of stopping at the first all-cached page (use to backfill suspected gaps). Sync is BOUNDED and RESUMABLE: on hosted deployments a per-call OFW-request budget (env OFW_SYNC_MAX_REQUESTS, or the maxRequests argument) caps how far one call walks; when the budget is hit the response reports done:false with a note — call again with the SAME arguments to resume. done:false means older history is still being backfilled; it does NOT mean recent messages are missing. Local installs are unbounded by default (done is always true).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
deepNoIf true, walk every OFW page until empty regardless of cache state. Use to backfill gaps. Default false.
foldersNoFolders to sync (default: all three). Must be non-empty if given — an empty list would sync nothing while reporting success.
maxRequestsNoMaximum OFW requests this single call may make before pausing. When hit, the response reports done:false — call again with the same arguments to continue. Omit to use the server default (OFW_SYNC_MAX_REQUESTS, or unbounded on local installs).
fetchUnreadBodiesNoIf true, also fetch bodies for unread inbox messages — which marks each one READ on OurFamilyWizard and stamps a co-parent-visible "First Viewed" time that cannot be undone. Defaults to the OFW_FETCH_UNREAD_BODIES env var (false unless set), and is forced off entirely when OFW_ALLOW_MARK_READ=false.
Behavior5/5

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

The description discloses critical behavioral traits beyond the readOnlyHint annotation: every call re-checks the newest page first, budget-based pausing and resumption, local vs. hosted unbounded behavior, and the irreversible mark-as-read effect of fetchUnreadBodies. This fully informs the agent of side effects and operational constraints.

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 comprehensive but somewhat verbose for the complexity of the tool. Every sentence is meaningful and well-organized, but some lines could be tightened without losing clarity. Overall, it balances detail with readability.

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?

The description covers all essential aspects: return values (counts, unread list), budget/resume mechanism, deep parameter for backfilling, mark-as-read implications, and local vs. hosted differences. Missing only minor details like error handling, but the complexity is well-addressed.

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?

Although the schema descriptions cover 100% of parameters, the tool description adds significant context: it explains the budget mechanism for maxRequests, the backfill logic for deep, the mark-as-read implication for fetchUnreadBodies, and the default behavior for folders. This enhances understanding beyond the schema alone.

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 the tool syncs messages from OurFamilyWizard into a local cache and returns counts per folder and a list of unread inbox messages without fetched bodies. It is distinct from sibling tools like ofw_get_message (fetches a specific message) and ofw_list_messages (lists messages), making its purpose unambiguous.

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?

The description provides explicit guidance on when to use this tool versus alternatives (e.g., call ofw_get_message on unread messages not fetched). It explains the bounded and resumable sync behavior, how to handle done:false responses, and the effect of the deep parameter for backfilling. It also warns that done:false does not mean recent messages are missing.

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