Familia

Get day overview

familia_get_day_overview

Read-only

Use this when the user asks for Familia items on a specific date or in a specific time window. Includes tasks, plans, and connected calendar events. Do not use for broad text search or multi-week availability.

Input Schema

TableJSON Schema

Name	Required	Description
`date`	No	Date as YYYY-MM-DD, ISO datetime, or omitted for today in the selected timezone.
`endAt`	No	Optional ISO datetime for a narrower time window. Defaults to one hour after startAt.
`startAt`	No	Optional ISO datetime for a narrower time window.
`timezone`	No	IANA timezone, defaults to ASYNQ_TIMEZONE or the local runtime timezone.
`householdId`	No	Optional Familia household id. Omit to aggregate across all accessible memberships.
`includeCompleted`	No	Include completed tasks when looking through history.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`date`	Yes
`count`	Yes
`items`	Yes
`links`	Yes
`counts`	Yes
`intent`	No
`window`	Yes
`timezone`	Yes
`householdId`	Yes
`overdueSummary`	Yes
`securityNotice`	Yes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed1 schema field changedSep 7, 2026

addedInput schema / properties / includeCompleted

Added value: +{
+  "description": "Include completed tasks when looking through history.",
+  "type": "boolean"
+}

First observedSep 6, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so safety and side effects are covered. The description adds that the tool includes tasks, plans, and connected calendar events, giving insight into its result content. No contradictions with annotations exist.

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 concise, consisting of two sentences that avoid redundancy. It front-loads the primary purpose and includes only essential clarifications about when not to use the tool, making it easy to parse.

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 the tool has an output schema and the description clarifies the scope of returned items (tasks, plans, events), an agent has enough context to invoke it correctly. The description also covers edge cases like 'omitted for today' and 'time window' by referencing the schema parameters, making it complete for this tool's complexity.

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?

The input schema has 100% description coverage for all six parameters, including formats and defaults. The tool description itself does not elaborate on parameters, but since the schema is already comprehensive, this meets the baseline without needing additional explanation.

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's function: retrieving Familia items (tasks, plans, calendar events) for a specific date or time window. It also distinguishes it from other tools by explicitly excluding broad text search and multi-week availability, which are covered by sibling tools like search_items and weekly_overview.

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 usage guidance: 'Use this when the user asks for Familia items on a specific date or in a specific time window' and warns 'Do not use for broad text search or multi-week availability.' This effectively tells the agent when to invoke this tool and when to consider alternatives.

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

All Familia tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?