taskfamily_list_pending_approvals

What it does

taskfamily_list_pending_approvals reads the approval queue on TaskFamily (taskfamily.com), the family site for chores, rewards kids choose, a private family chat and helpers. It returns two arrays: approvals, meaning chores a kid has finished and submitted for a parent to sign off, and redemptions, meaning rewards a kid has asked for with their points.

It is a Read tool. It changes nothing on the account, it is idempotent, and calling it twice in a row returns the same picture as long as nothing changed in between. Nothing is approved, rejected or spent by this call. If both arrays come back empty, the account has nothing waiting.

When an assistant should call it

Call it when a parent asks anything like what is waiting for me, what did the kids finish today, or which rewards are pending. It is the right first step before a parent makes decisions, because the answer names each kid, what was submitted or requested, and the points involved.

It also works well as part of a short routine: read the pending approvals, then read taskfamily_list_tasks to see what is still open, and taskfamily_list_upcoming_events to see what is coming up on the family calendar. Do not call it on a loop or poll it; call it when a question actually needs the queue.

Inputs and an example call

The tool takes no arguments. Send an empty arguments object. There are no filters for kid, date or type, so you get the pending chores and the pending reward requests in one response.

Call it over the account connector at https://onelifevibe.com/mcp with JSON-RPC 2.0:

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

The connector needs the person's OneLifeVibe sign-in (OAuth 2.1 with PKCE) and the scope olv.read. The person must also have signed in to taskfamily.com with OneLifeVibe once.

What comes back

The result holds two arrays. Each item in approvals has id, kid_name, title, submitted_at and points, where title is the chore that was finished and submitted_at is when it came in. Each item in redemptions has id, kid_name, reward, points and requested_at, where reward is the thing the kid asked for and requested_at is when the request was made.

Use id when you refer to a specific entry in a follow-up question or when a parent wants to talk about one item. Read the arrays in order of what a parent would care about, and say plainly how many chores and how many reward requests are waiting. Points values and timestamps come straight from the account; report them as returned rather than recalculating or reformatting dates into a different time zone.

Errors, limits and safety

The common failure is not_linked. It means the person has not signed in to taskfamily.com with OneLifeVibe at least once. Have them do that, then call the tool again. If the sign-in itself fails, check that the client completed the OAuth 2.1 PKCE flow and requested the scope olv.read.

The connector's sign-in is set up for Meta Muse today, under the client name onelifevibe-muse. Other MCP clients reach the no-account tools through the free connector.

On the platform API side, taskfamily_list_pending_approvals is listed in GET /api/platform/v1/tools, but a platform key gets 501 world_tools_unavailable for it today, because the tool acts on one member's own data. A platform key can call the world catalogue, the tool registry, the network directory tool and the event log.

Because this is a read tool, it is safe to retry after a network error. Do not present its output as an approval, and do not tell a parent that something has been accepted; the call only reports what is waiting.