Familia

Create list task

familia_create_list_task

Destructive

Use this when the user asks to create a shopping list, packing list, checklist, or Familia task with list items. If the same list task repeats across several days, weeks, or months, provide repeatRule and create one recurring list task instead of multiple one-time tasks. Do not use when editing an existing list attachment. Assigning to another household member queues a push notification; schedules can also queue reminders, and delivered notifications cannot be recalled.

Input Schema

TableJSON Schema

Name	Required	Description
`dueAt`	No	Accepts YYYY-MM-DD for all-day items or an RFC 3339 datetime. When using a datetime without an offset, provide timezone.
`items`	Yes	Checklist items to attach to the new task. Supports nested subtasks.
`title`	Yes	Task title, e.g. “Groceries” or “Pack for trip”.
`allDay`	No	Whether the due date is an all-day task.
`timezone`	No	IANA timezone for dueAt, e.g. Europe/Prague.
`listTitle`	No	Optional title shown on the attached list. Defaults to the task title.
`repeatRule`	No	Optional RFC 5545 RRULE, e.g. FREQ=DAILY;INTERVAL=2 or FREQ=WEEKLY;BYDAY=MO,WE. Use this when the user says the same task or plan repeats across days, weeks, or months; create one recurring schedule instead of multiple one-time items unless each occurrence has different content. Requires the first dueAt/startAt as the anchor.
`description`	No	Optional task details, notes, or context.
`householdId`	Yes	Familia household id where the list task should be created.
`leadMinutes`	No	Reminder lead time in minutes before dueAt. Defaults to 0.
`ownerUserId`	No	Optional Familia user id that owns the task.
`assigneeUserId`	No	Optional Familia user id responsible for the task.
`idempotencyKey`	No	Optional stable retry key. Reusing the same key for the same create operation returns the original result instead of creating a duplicate.
`recurrenceEndDate`	No	Optional YYYY-MM-DD end date for a recurring schedule. Use this for bounded repeats such as "this week", "for three days", or "until Sunday".

Output Schema

TableJSON Schema

Name	Required	Description	Default
`taskId`	No
`deeplink`	Yes
`schedule`	No
`agreementId`	Yes
`attachmentError`	No
`attachmentCreated`	No
`todoListAttachment`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 6, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the mutation profile is known. The description goes beyond this by disclosing side effects: assigning to another household member queues a push notification, schedules can queue reminders, and delivered notifications cannot be recalled. This adds meaningful behavioral context without contradicting the annotations.

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?

Four sentences with zero filler. The trigger is front-loaded, and each sentence carries distinct value: when to use, recurrence guidance, exclusion, and side effects. It is appropriately sized for a tool with this complexity.

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 14 parameters but 100% schema coverage and a present output schema, the description covers the key decision points: routing, recurring-list handling, exclusion for editing, and side effects. An agent has enough context to invoke the tool correctly without missing critical information.

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 description coverage is 100%, so the baseline is 3. The description adds decision-relevant semantics for repeatRule (use for recurring tasks rather than multiple one-time tasks) and for assigneeUserId (notification side effect), which goes beyond the schema's field-level descriptions.

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 states a specific trigger ('use this when the user asks to create a shopping list, packing list, checklist, or Familia task with list items') with a clear verb and resource. It also explicitly excludes editing existing list attachments, which distinguishes it from sibling tools without requiring the agent to open their schemas.

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?

Gives an explicit when-to-use condition and a when-not-to-use exclusion ('Do not use when editing an existing list attachment'). It also provides decision guidance for recurring tasks: if the list repeats, provide repeatRule and create one recurring task instead of many one-time tasks, which helps the agent choose the right approach.

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

Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?