taskfamily_list_tasks

What it does

taskfamily_list_tasks returns the chores and tasks on a TaskFamily household's list for a single day or a short window of days. TaskFamily (taskfamily.com) is where families keep chores, the rewards kids choose, and a private family chat. This tool covers the chore and task side: it reads what is scheduled and which child it belongs to.

The tool defaults to today in the family's own timezone, so an assistant does not have to work out the date before asking. Pass date to look at a specific day, or days to widen the window to as many as seven days starting from date or from today.

It is a Read-class tool. It changes nothing, and calling it twice with the same arguments returns the same list.

When an assistant should call it

Call it when someone asks what the kids have to do today, what is coming up this week, or which child a particular task belongs to. It is also the right first step before an assistant reminds anyone about chores: read the list, then talk about what is actually there.

Use it for planning across the next few days — days set to 3 gives a three-day view. Reach for taskfamily_list_pending_approvals when the question is about approvals still waiting on a parent, taskfamily_list_upcoming_events for the calendar side, and taskfamily_add_event when something new needs to be added to the schedule.

Keep the window within the limit. A single call covers at most seven days, so a longer horizon means several calls rather than one big one.

Inputs and an example call

There are two optional arguments. date takes a date in YYYY-MM-DD form and sets the first day of the window. days takes an integer from 1 to 7 and sets how many days to cover. Send neither and you get today.

The tool runs on the OneLifeVibe account connector at https://onelifevibe.com/mcp. The person signs in with OAuth 2.1 with PKCE, the call needs the scope olv.read, and the person must have signed in to taskfamily.com with OneLifeVibe at least once.

A JSON-RPC tools/call for a three-day list:

{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"taskfamily_list_tasks","arguments":{"days":3}}}

For one specific day, send {"date":"YYYY-MM-DD"} as the arguments instead, or send an empty arguments object for today.

What comes back

The response carries a tasks array. Each entry has six fields: id, kid_name, title, due_date, status and points. id identifies the task, kid_name says which child it belongs to, title is the task itself, due_date is the day it falls on, status shows where it stands, and points is its value in the family's reward system.

kid_name is what makes the list practical for a family assistant. One call covers every child in the household, so group the entries by kid_name instead of calling once per child.

Errors, limits and safety

The failure you are most likely to hit is not_linked. It means the person signed in to the connector but has never signed in to taskfamily.com with OneLifeVibe, so there is no household to read. Ask them to sign in at taskfamily.com once, then retry the call.

The connector's sign-in is set up for Meta Muse today under the client onelifevibe-muse; other MCP clients reach the no-account tools through the free connector. The tool also appears in the platform tool registry at GET /api/platform/v1/tools, but a platform key calling it gets 501 world_tools_unavailable, because it acts on one member's own data. A platform key is for the world catalogue, the tool registry, the network directory tool and the event log.

Nothing here writes, so there is no confirmation step to build and no risk of a retry duplicating work. Keep days between 1 and 7 and send date as YYYY-MM-DD.