Familia

Create list task

familia_create_list_task

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.

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. Dates show when Glama detected each change.

First observedSep 6, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations only indicate readOnlyHint=false and destructiveHint=false, so the description adds meaningful behavior: it is a creation operation and explains that repeated lists should become a single recurring task, not multiple one-time tasks. This is useful behavioral context not carried by the annotations alone.

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 appropriately concise: two sentences with a clear front-loaded trigger condition, a recurrence rule, and an explicit anti-use case. No filler or repetition of schema fields.

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?

Given the rich input schema, output schema, and annotations, the description covers the key decision points: when to create a list task and how to handle recurring lists. It could have explicitly named the sibling for plain task creation (familia_create_task) or standalone list attachments, but the existing exclusions make it sufficiently complete.

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 description coverage is 100%, so the schema already documents all 14 parameters thoroughly. The description adds a high-level note about repeatRule, but it does not add new parameter meaning beyond what the schema already provides; a baseline of 3 is appropriate.

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 identifies the verb (create) and resource (list task), and lists concrete trigger examples: shopping list, packing list, checklist, or any Familia task with list items. It also distinguishes the tool from editing an existing list attachment, which is a sibling operation.

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?

It explicitly states when to use the tool ('Use this when...'), gives a conditional rule for recurring lists via repeatRule, and includes a clear exclusion ('Do not use when editing an existing list attachment'). This gives an agent actionable routing guidance beyond the schema.

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?