wuuuh_list_action_plan

What it does

wuuuh_list_action_plan is a read tool on WUUUH (wuuuh.com), the site built around losing your income: your next best move, official links and mutual aid. It returns the items in the signed-in person's action plan so an assistant can answer questions like what is still open, what comes due next, or what was skipped. Read means it changes nothing: no item is created, edited or removed by this call.

Each call returns at most the number of items you ask for, and you can narrow the result to a single status. The tool is idempotent, so repeating the same call gives you the same view of the plan with no side effects.

When an assistant should call it

Call it when someone asks about their own plan: what is on it, what is still todo, what is in progress, what is done, what they skipped, or which items are due. It also works as a confirmation step right after wuuuh_set_action_item_status, so the assistant reads back the new state instead of assuming the change landed.

For a wider view of the person's WUUUH situation, wuuuh_get_dashboard covers the overview; this tool is the list itself. Do not reach for it when the request concerns another website or when the person wants to change an item rather than read it.

Inputs and an example call

There are two optional arguments. status takes one of todo, doing, done or skipped and returns only items in that state; leave it out to get items in every state. limit is an integer from 1 to 50 and sets how many items come back, defaulting to 10.

The call goes to the account connector at https://onelifevibe.com/mcp. It needs the person's OneLifeVibe sign-in through OAuth 2.1 with PKCE and the scope olv.read, and the person must have signed in to wuuuh.com with OneLifeVibe at least once. Without that, the answer is not_linked.

{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"wuuuh_list_action_plan","arguments":{"status":"todo","limit":10}}}

What comes back

A result carrying an items array. Every entry has id, title, status, due_at and category: the status is one of the four filter values, due_at holds the item's due date, and category groups the item by the kind of action it is. An empty array means the plan has no items matching the filter you sent, not that the call failed.

Keep the ids. They are what wuuuh_set_action_item_status needs when the person wants to move an item to another status. The tool applies the filter and the limit; if order matters to the person, sort the returned items by due_at on your side before you present them.

Errors, limits and safety

not_linked means the OneLifeVibe sign-in has no WUUUH connection for this person yet. Have them sign in to wuuuh.com with OneLifeVibe once, then retry; there is nothing to reset on the connector side.

A platform key cannot call this tool. It is listed in GET /api/platform/v1/tools, but a platform key gets 501 world_tools_unavailable for it, because the tool acts on one member's own data. Platform keys stay with the world catalogue, the tool registry, the network directory tool and the event log.

The account connector's sign-in is set up for Meta Muse today (client onelifevibe-muse). Other MCP clients reach the no-account tools through the free connector. Keep limit inside 1 to 50. The tool reads, is idempotent and is not destructive, so retries are safe and no confirmation step is needed.