Glossary

tool name

A tool name is the lowercase identifier a client sends in tools/call to run one specific tool on a server.

Updated November 15, 2026

Also called
tool identifier

At OneLifeVibe

What it means

A tool name is the lowercase string a client puts in a tools/call request to say which tool it wants to run. In MCP a server publishes a set of tools, each one a named operation with an input schema, and the name is how you address the one you need. It is the value of the name field. It is not a title or a display label.

Think of it as a function name that crosses a network boundary. Your code never calls the tool directly. It sends the name and a set of arguments, and the server decides what to do with them. That makes the name part of the public contract: if it changes, every client that hardcoded it breaks.

How it works

A client usually starts with tools/list, which returns the available tools with their names and input schemas. The name tells you what exists. The schema tells you what to send. Then tools/call carries the name plus an arguments object, wrapped in a JSON-RPC 2.0 request over the connection's transport.

The server looks up the name, checks the arguments against the schema, and runs the tool. If the name is unknown there is nothing to dispatch, so you get an error back instead of a result. If the name is right but the arguments do not fit the schema, that fails too. Both cases are cheap to avoid: read the list first, validate before you send.

How OneLifeVibe uses it

OneLifeVibe runs one connector for a network of independent websites, so tool names carry a website prefix to keep them apart. Every name is lowercase with underscores, and the prefix names the site it belongs to: senatus_, wuuuh_, helpbless_ and so on. A name starting with senatus_ is a senatus tool. The prefix is part of the name, not a separate setting you choose.

To see what is available, call GET /api/platform/v1/tools. It lists every tool and its input schema, which answers both questions at once: what do I call it, and what do I send. Pass the name exactly as listed in your tools/call request. When the list changes, refetch it rather than assuming yesterday's names still work.

Common mistakes

Dropping the prefix because it looks redundant. It is not. The prefix is how the connector keeps senatus_ and wuuuh_ tools distinct, and a name without it will not match anything.

Guessing a name from a page title or a display name, or changing the casing to camelCase out of habit. Names are lowercase with underscores.

Sending arguments that do not match the returned input schema. Fetch the schema, check the required fields and their types, then send. And cache the list instead of calling GET /api/platform/v1/tools on every request.

Questions

How do I find the tool names OneLifeVibe exposes?

Call GET /api/platform/v1/tools. It returns every tool with its input schema. Use the names exactly as they come back.

What does the prefix on a tool name mean?

It is the website the tool belongs to, such as senatus_, wuuuh_ or helpbless_. Names are lowercase with underscores, and the prefix is part of the name you send in tools/call.

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.