Assistant tool

olv_list_worlds

Read-only: lists every independent website in the OneLifeVibe network, what each is for, and its address. No linked accounts.

Updated November 6, 2026

Website
OneLifeVibe hub
Class
Read
Returns
worlds[]: key, name, domain, what, adult, url

List every independent website in the OneLifeVibe network, what each one is for, and its address. Works without any linked accounts.

Where you can call it

Inputs

ArgumentTypeNotes
No arguments.

Example request

POST https://onelifevibe.com/mcp

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

Other hub tools

What it does

olv_list_worlds is a Read tool on the OneLifeVibe hub. It returns the network directory: every independent website in the OneLifeVibe network, a description of what each one is for, and its address. The call takes no arguments and changes nothing, so it is safe to repeat.

Each entry exposes key, name, domain, what, adult and url. key is the world identifier used elsewhere, name is the display name, domain and url give the address, what describes the purpose, and adult carries the adults-only flag.

The tool works without any linked accounts. It is idempotent and non-destructive; it creates, updates and deletes nothing.

When an assistant should call it

Call olv_list_worlds when the person asks what sites are in the OneLifeVibe network, what a particular world is for, or which address belongs to a world. It is also the lookup step when you have a world key or name and need the matching domain or url before calling a world-specific tool.

Use it for directory questions, not for profile data. If the request is about a person or a world profile, use olv_get_profile instead. The hub also exposes find_free_tools, list_situations and gift_ideas for other tasks.

Because the tool has no inputs, there is nothing to disambiguate before the call. Make the call, then answer from the returned fields. If the list does not contain the world the person named, say so instead of guessing a domain or url.

Inputs and an example call

Inputs: none. Send an empty arguments object. On the account connector at https://onelifevibe.com/mcp, use the MCP tools/call method with name olv_list_worlds:

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

On the platform API, send POST https://onelifevibe.com/api/platform/v1/tools/olv_list_worlds with an olvp_ key holding tools:invoke. The account connector needs the person's OneLifeVibe sign-in, using OAuth 2.1 with PKCE and scope olv.read. Its sign-in is set up for Meta Muse today (client onelifevibe-muse).

What comes back

The result contains a worlds array. Each element has key, name, domain, what, adult and url. The return shape is the worlds array; the tool defines no pagination, sorting or filtering parameters. If you need a subset, filter the returned list on your side.

Use key when another call or record expects a world identifier. Use domain and url when you need the address to show or route to. Use what for a plain description of the world's purpose. The adult flag tells you whether the world is adults-only; describe those worlds plainly and neutrally.

Errors, limits and safety

olv_list_worlds has no arguments, so there are no input validation cases to handle. Authorization still applies. On the account connector, a missing or insufficient OneLifeVibe sign-in blocks the call; reauthenticate with OAuth 2.1 with PKCE and scope olv.read. On the platform API, use an olvp_ key holding tools:invoke.

The tool is Read, non-destructive and idempotent. It changes nothing, so a retry after a network or authorization failure is safe once the credential is fixed. Do not treat a failed call as an empty network; surface the failure and try again or switch to the other callable route.

No plan is required for this tool. It works without any linked accounts, but it does not bypass caller authorization. The response is directory data, so there is no write, delete or destructive action to confirm.

Questions

Do I need a OneLifeVibe account to call olv_list_worlds?

You need an authorized caller, not a linked website account. On the account connector, sign in with OneLifeVibe using OAuth 2.1 with PKCE and scope olv.read; on the platform API, use an olvp_ key holding tools:invoke.

What does each entry in the worlds array contain?

Each entry has key, name, domain, what, adult and url. key identifies the world for later calls, domain and url give its address, and what describes what the world is for.

Can I call olv_list_worlds from an MCP client other than Meta Muse?

The account connector at https://onelifevibe.com/mcp is set up for Meta Muse today (client onelifevibe-muse). For other clients, the platform API route is POST https://onelifevibe.com/api/platform/v1/tools/olv_list_worlds with an olvp_ key holding tools:invoke.

Build with it. Connect an assistant to https://onelifevibe.com/mcp, or get a free Sandbox key for the Platform API.

Get a free key Connector guide

Written from the OneLifeVibe tool registry and platform configuration, and checked automatically before publishing. Something wrong? Tell us.