Skip to main content
Glama
chrischall

OurFamilyWizard MCP

by chrischall

ofw_list_messages

List messages from OurFamilyWizard with filters for folder, date range, and keyword search, and auto-refresh to ensure verified results.

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. Returns an explicit complete boolean describing the RESULT SET: true means "this is every message on OurFamilyWizard matching these filters as of freshness.asOf" — check it before asserting a count. An empty result from a cache that is not verified-fresh is REFUSED (result:"UNVERIFIED_EMPTY") rather than reported as an absence; pass autoRefresh:true to sync and answer instead.

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")
autoRefreshNoIf the result comes back EMPTY from a cache that is not verified-fresh, sync the backing folders first and answer from the refreshed cache instead of refusing. Defaults to the OFW_AUTO_REFRESH env var (false unless set), in which case the call refuses with result:"UNVERIFIED_EMPTY" and names the remedy. Costs OFW requests when it fires.
Behavior5/5

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

The description explains the `complete` boolean semantics, the UNVERIFIED_EMPTY refusal behavior, and autoRefresh fallback. It also notes potential large result sets (1000+). Annotations (readOnlyHint: false) are consistent, and the description adds crucial context 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.

Conciseness3/5

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

The description is information-dense but runs as a single paragraph. It could benefit from bullet points or structure for easier scanning. However, it remains clear and every sentence adds value.

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

Completeness4/5

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

With 7 parameters and no output schema, the description covers the return behavior (result field, `complete` boolean) and edge cases (UNVERIFIED_EMPTY). It also references caching and syncing, which is relevant given sibling tools like ofw_sync_messages and ofw_check_freshness. Lacks explicit return value structure, but adequate.

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?

Schema coverage is 100%, but the description adds meaning: explains that `q` is a substring on subject AND body, `folderId` defaults to 'both', `since`/`until` are inclusive/exclusive, and `autoRefresh` defaults to an env var. This extra detail justifies a score above baseline 3.

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 'List messages from the local OurFamilyWizard cache' and details filtering by folder, date range, and substring query. It distinguishes from siblings like ofw_get_message (single message) and ofw_send_message (send).

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 advises preferring filters over pagination ('if you know what you want...prefer the filters over walking pages') and explains when to use autoRefresh. It does not explicitly contrast with alternative tools like ofw_sync_messages or list drafts, but provides clear context.

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