supportmeet_find_help

What it does

supportmeet_find_help is a read tool on SupportMeet (supportmeet.com). You give it one situation, such as caregiver-burnout, and it returns the help SupportMeet matches for that situation in a country: crisis lines, charities, government programmes, peer groups and professionals, each with a phone number and a link.

The tool changes nothing. It looks up the matches and hands them back, and the whole answer arrives in one call. Country defaults to the country on the person's SupportMeet account when you leave it out. It is free to use, and nothing is sent to anyone.

When an assistant should call it

Call it when someone describes a situation and needs real contacts rather than conversation: where to get help, which service covers their area, or who to phone. It is the lookup step, not the talking step.

Get the situation key first. supportmeet_list_my_circles returns the keys that person's circles use, and supportmeet_find_help expects one of those keys exactly. If the person asks about a country other than their own, pass country as a two-letter code so the matches are local to where they are.

Inputs and an example call

Three arguments. situation is required: the situation key as supportmeet_list_my_circles returns it, for example caregiver-burnout, up to 80 characters. country is optional and must match ^[A-Za-z]{2}$, a two-letter code; omit it for the country on the person's SupportMeet account. limit is optional, an integer from 1 to 20, and defaults to 8.

Send a tools/call request to https://onelifevibe.com/mcp with params.name set to supportmeet_find_help. In params.arguments pass situation caregiver-burnout and limit 10. Keep id on the request so you can pair the response with the call.

The endpoint needs the person's OneLifeVibe sign-in (OAuth 2.1 with PKCE) and the olv.read scope. Its sign-in is set up for Meta Muse today (client onelifevibe-muse); other MCP clients reach the no-account tools through the free connector.

What comes back

The response repeats the situation as key, name and category, and gives the country that was used. help is a list where each match carries name, kind, description, phone, url, cost and verified. crisis is a separate list of crisis lines with name, phone and url, and the top-level url points to the SupportMeet page for the situation.

Check crisis before you write anything to the person. If it has entries, put those phone numbers first, then the broader list of charities, programmes, groups and professionals. cost and verified are there so you can show which entries are free and which have been checked.

Errors, limits and safety

not_linked comes back when the person has not signed in to supportmeet.com with OneLifeVibe at least once. Ask them to sign in there, then retry the same call. No other account setup is needed beyond that one sign-in and the olv.read scope on the connector.

On the Platform API, supportmeet_find_help is listed in GET /api/platform/v1/tools, but a platform key gets 501 world_tools_unavailable for it today, because it 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.

limit tops out at 20 and defaults to 8, so raise it on purpose rather than leaving it high by habit. The tool is read only, idempotent and not destructive: calling it twice gives you the same matches and changes nothing on the account. It is free, and nothing about the person is sent to the organisations it returns.