helpbless_save_need

What it does

helpbless_save_need is a Write tool for HelpBLESS (helpbless.com), where people ask for money, time, skills or advice and gifts go straight to a person. The tool saves a need so the person can find it later, or removes it from the saved list. Saving is private. HelpBLESS can send an in-app notice when a saved need is solved.

It changes only that person's own data on HelpBLESS. It is not destructive, it is idempotent, and repeating the same request has no further effect. Set saved to true to save and false to remove. The need is identified by need_id.

When an assistant should call it

Call it when the person asks an assistant to keep a HelpBLESS need for later, or to stop keeping it. Typical phrasing is save that need for later, keep this need, or remove this need from my saved list. The assistant needs a need_id first; HelpBLESS listing tools on the same website include helpbless_list_my_needs, helpbless_list_my_gifts and helpbless_list_saved_needs.

Use helpbless_list_saved_needs to check the current saved list before deciding whether a save or an unsave is needed. The tool only sets the saved state for one need; it does not create a need, give a gift or change any other part of a need.

Because it is a Write tool, reserve it for an explicit request from the person. A request to save an already saved need is harmless: the call returns the same saved state and has no further effect.

Inputs and an example call

Both inputs are required. need_id is a string of up to 80 characters that identifies the need. saved is a boolean: true saves the need, false removes it from the saved list.

Send a JSON-RPC tools/call request to https://onelifevibe.com/mcp. For example: {"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"helpbless_save_need","arguments":{"need_id":"<need_id from helpbless_list…>","saved":true}}}

The Account connector needs the person's OneLifeVibe sign-in (OAuth 2.1 with PKCE) and the scope olv.write. The person must also have signed in to helpbless.com with OneLifeVibe once, otherwise the tool answers not_linked.

What comes back

The response returns need_id and saved. saved is the state after the call: true means the need is in the person's saved list, false means it is not.

Because the tool is idempotent, sending the same need_id and saved value again produces the same result. If the person wants to review what is saved, call helpbless_list_saved_needs.

A successful save is private. HelpBLESS can send an in-app notice when a saved need is solved.

Errors, limits and safety

The schema requires both inputs: need_id as a string of no more than 80 characters and saved as a boolean. Repeating a request is safe because the tool is idempotent and not destructive.

If the Account connector has no linked HelpBLESS sign-in, the tool returns not_linked. Have the person sign in to helpbless.com with OneLifeVibe once, then retry. The connector requires OAuth 2.1 with PKCE and the scope olv.write.

A platform key cannot call this tool today: 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. The connector's sign-in is set up for Meta Muse today with client onelifevibe-muse; other MCP clients reach the no-account tools through the free connector.