Skip to main content
Glama
chrischall

OurFamilyWizard MCP

by chrischall

ofw_list_messages

Read-only

Retrieve co-parenting messages from your local OurFamilyWizard cache with filters by folder, date range, or subject/body search. Sync first if cache is empty.

Instructions

List messages from the local OurFamilyWizard cache. Supports filtering by folder, date range, and a substring query on subject+body. Pagination is offset-based but if you know what you want (a date range, a topic), prefer the filters over walking pages — the cache may have 1000+ messages. Call ofw_sync_messages first if the cache is empty or stale.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoSubstring match on subject AND body (case-insensitive). Use to find messages on a specific topic.
pageNoPage number (default 1)
sizeNoMessages per page (default 50)
sinceNoISO date or datetime — only messages with sent_at >= since (inclusive)
untilNoISO date or datetime — only messages with sent_at < until (exclusive)
folderIdNoFolder name: "inbox", "sent", or "both" (default "both")
Behavior4/5

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

Annotations declare readOnlyHint=true, consistent with description. Adds context about cache size and pagination behavior beyond annotations.

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?

Three sentences, concise, front-loaded with purpose. Could be slightly trimmed but efficient.

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

Completeness3/5

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

No output schema, and description does not explain return structure. Provides useful context about caching and pagination, but lacks output details.

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 coverage is 100%; description largely duplicates schema descriptions. Adds general advice on using filters but no new param-specific semantics.

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 it lists messages from the local cache, with filtering. It distinguishes from sibling tools like ofw_list_drafts and ofw_list_events.

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?

Provides explicit guidance: call ofw_sync_messages first if cache is stale, prefer filters over pagination. Does not explicitly exclude alternatives but implies best practices.

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