wuuuh_get_dashboard

What it does

wuuuh_get_dashboard is a read tool on the OneLifeVibe account connector. One call returns the state of a person's WUUUH dashboard: their country, whether an income-loss event is active, that event's kind and start date, their plan, and how many action items are open and done. WUUUH is the OneLifeVibe website for people who have lost income, covering the next best move, official links and mutual aid, and it serves the US, Canada and the UK.

Read tools change nothing, and this one takes no arguments. You cannot move an action item or edit a plan with it. It is the snapshot you take before deciding what to do next. Two companion tools cover the rest of the workflow: wuuuh_list_action_plan returns the plan items themselves, and wuuuh_set_action_item_status changes the status of one item.

When an assistant should call it

Call it at the start of any conversation where the person asks what to do about lost income, where they stand, or what is left on their plan. One call gives you the context that would otherwise take several questions: whether an income-loss event is open and how far through the action plan they are.

Use it before wuuuh_list_action_plan when you only need the headline counts, and skip it when the person has already told you they want to change something. In that case read the plan, then go to wuuuh_set_action_item_status. If no income event is active, the dashboard says so, which is still useful context before you suggest recovery steps.

It answers questions about one member's own dashboard, not about WUUUH in general.

Inputs and an example call

The tool has no inputs. Send an empty arguments object. Identity travels with the connection: the account connector at https://onelifevibe.com/mcp uses OAuth 2.1 with PKCE, needs the person's OneLifeVibe sign-in, and requires the olv.read scope.

Post this to https://onelifevibe.com/mcp:

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

What comes back

Six fields, flat and easy to map. country is the member's WUUUH country. has_active_income_event is a boolean. income_event carries kind and started_at. plan describes the member's plan. stats holds action_items_open and action_items_done.

Use the two counts to describe progress without relisting every item, and pull the items themselves with wuuuh_list_action_plan when the person wants detail. The call is idempotent, so you can repeat it after a status change to confirm the new totals.

Errors, limits and safety

not_linked is the error you will see most. It means the person has signed in to OneLifeVibe but has not signed in to wuuuh.com with OneLifeVibe once, so there is no WUUUH dashboard for the connector to read. Ask them to sign in at wuuuh.com with their OneLifeVibe account, then call the tool again.

A platform API key cannot call this tool. It is listed in GET /api/platform/v1/tools, but the call returns 501 world_tools_unavailable 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. Use the account connector for this one.

On the connector, authorization completes before the tool runs, so request olv.read up front. Meta Muse is set up today with the client onelifevibe-muse, and other MCP clients reach the no-account tools through the free connector. The tool is read-only and idempotent: calling it again leaves the dashboard unchanged.