Skip to main content
Glama
chrischall

OurFamilyWizard MCP

by chrischall

ofw_get_message

Retrieve a specific message or draft from OurFamilyWizard by ID, controlling whether unread inbox messages are marked as read to avoid irreversible co-parent-visible changes.

Instructions

Get a single OurFamilyWizard message OR draft by ID. Reads from local cache when available; otherwise fetches from OFW — and for an UNREAD INBOX message that fetch marks it read and stamps a "First Viewed" time the co-parent can see, which is part of the record and cannot be undone. Pass allowMarkRead:false to refuse such a fetch instead (cached bodies, sent messages and already-read messages are unaffected, because none of them stamp anything). For ids that match a draft (in the drafts cache), the response carries folder="drafts" and the body/subject/recipients reflect the drafts cache (which ofw_sync_messages keeps fresh) — drafts have no fromUser, and sentAt/fetchedBodyAt mirror the draft's modifiedAt. For inbox/sent messages, folder is "inbox" or "sent" as before.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
messageIdYesMessage ID (also accepts draft IDs — drafts are routed via the drafts cache)
allowMarkReadNoDefault true (the long-standing behaviour). Set false to refuse a fetch that would mark an unread INBOX message as READ on OurFamilyWizard — an irreversible, co-parent-visible change to the record. Reads that cannot stamp anything (a cached body, a sent message, an already-read message) still succeed. The server-wide OFW_ALLOW_MARK_READ=false is a ceiling this argument cannot raise.
Behavior5/5

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

The description discloses key behavioral traits beyond annotations: fetching an unread INBOX message marks it read and stamps a 'First Viewed' time visible to the co-parent, which is irreversible. It also explains caching, draft behavior, and the effect of allowMarkRead. No contradiction with annotations (readOnlyHint: false).

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 moderately sized and front-loaded with the main purpose. Every sentence adds value, though it could be slightly more concise. It remains clear and well-structured.

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?

Given no output schema, the description adequately explains return values (folder, fromUser, sentAt, etc.) for different scenarios (draft vs inbox). It covers all important aspects for an agent to use the tool correctly.

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?

The description adds significant meaning beyond the schema, explaining that messageId accepts draft IDs, default behavior of allowMarkRead, and the server-wide ceiling. With 100% schema coverage, the description still enhances understanding.

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 'Get a single OurFamilyWizard message OR draft by ID.' This verb+resource definition is specific and distinguishes from sibling tools like ofw_list_messages or ofw_list_drafts.

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 explicit guidance on when to use the tool, including handling of drafts, unread messages, and the allowMarkRead parameter. However, it does not explicitly mention when not to use it or direct 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