Glossary

Tool registry

A tool registry is the list of tools a platform can call, with schemas for each one. OneLifeVibe serves its registry at GET /api/platform/v1/tools.

Updated November 13, 2026

Also called
tools endpoint, platform tool registry

At OneLifeVibe

Related terms

What it means

A tool registry is an index of the operations a platform can call. Each entry gives a tool a name and describes the inputs it accepts and the result it returns, usually with a schema. A client reads the registry to learn what it can do without hardcoding a list. You may see it called the tools endpoint or the platform tool registry.

The registry is not the endpoint that runs a tool. It is the catalog you fetch first. For MCP, tools are the callable operations a client can request, and each one needs a description of its arguments so the caller can build a valid request. The exact fields depend on the platform, so read the schema in the response instead of assuming a shape.

How it works

You fetch the registry with an HTTP GET and read the tool entries. A typical entry has a name, a description, an input schema, and sometimes a flag that says who can call it. Validate your arguments against the input schema before you send them. That catches missing fields and wrong types early.

The response is a snapshot of the tools at that moment. Fetch it when your client starts, cache it, and refresh it when you need to. If you call a name that is not in the registry, expect an error such as 404 or 400, depending on how the API handles unknown tools. Treat the registry as the source of truth for names and arguments, not a copied list.

How OneLifeVibe uses it

OneLifeVibe serves its tool registry at GET /api/platform/v1/tools. Every approved OneLifeVibe Platform client starts on the free Sandbox. That gives you one key for the world catalog, the tool registry, the network directory tool and the event log, with 1,000 calls a day at 10 requests a minute. No card is needed, and Sandbox has no webhooks.

A platform key can call the world catalog, the tool registry, the network directory tool (olv_list_worlds) and the event log. GET /tools marks each tool with callable_with_platform_key. Read that flag when you build a client: it tells you whether the tool is callable with the platform key you hold. For a person's own data, connect an assistant to the account connector at https://onelifevibe.com/mcp, where the person signs in.

Fetch the registry before you wire up calls. Build each request from the schema in the entry, and check callable_with_platform_key so you do not send a platform key to a tool that is not callable that way.

Common mistakes

Do not hardcode tool names or argument shapes from an old response or a blog post. Fetch GET /api/platform/v1/tools and build from the current entry. Also check callable_with_platform_key before you use a platform key. A tool in the registry is not automatically callable with that key.

Another mistake is fetching the registry on every request. Cache it and refresh deliberately. Do not confuse the registry with the account connector at https://onelifevibe.com/mcp. The registry tells you what tools exist. The connector is where a person signs in for their own data.

Questions

What does GET /api/platform/v1/tools return?

It returns the OneLifeVibe tool registry: the tools a platform can call, with their schemas. Each entry is marked with callable_with_platform_key.

Can I call any tool in the registry with a platform key?

Only tools marked with callable_with_platform_key are callable with a platform key. A platform key can call the world catalog, the tool registry, the network directory tool (olv_list_worlds) and the event log. For a person's own data, use the account connector at https://onelifevibe.com/mcp, where the person signs in.

See it working. The OneLifeVibe connector and Platform API put these pieces together.

Get a free key Read the docs

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