Glossary
tools/call
tools/call is the MCP method that runs one named tool with arguments. On OneLifeVibe it is a single POST that returns a single JSON answer.
Updated November 12, 2026
- Standard
- Model Context Protocol specification
At OneLifeVibe
- Methods: initialize, ping, tools/list and tools/call; resources/list and prompts/list answer with empty lists. Notifications are accepted with 202.
- Both OneLifeVibe connectors use Streamable HTTP with JSON responses and no server-sent event stream: every tools/call is one POST that returns one JSON answer.
- MCP messages to https://onelifevibe.com/mcp are JSON-RPC 2.0 over POST, for example {"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"olv_list_worlds","arguments":{}}}.
- https://onelifevibe.com/mcp/free is a Streamable HTTP MCP server with JSON responses, stateless, no sign-in. Methods: initialize, ping, tools/list, tools/call.
Related terms
What it means
tools/call is a JSON-RPC 2.0 method defined by the Model Context Protocol. A client sends it to run one named tool with a set of arguments, and the server sends back that tool's result. The method sits alongside setup and discovery calls: initialize, ping, tools/list, and the resources/list and prompts/list methods, which answer with empty lists.
The request carries a name and an arguments object. The name is the tool identifier exactly as tools/list reported it. The arguments object holds the inputs for that tool. The response comes back on the same JSON-RPC id, either as a result or as an error.
How it works
Every call is an HTTP POST to the MCP endpoint. The body is a JSON-RPC 2.0 object with jsonrpc, id, method and params.
OneLifeVibe's connectors use Streamable HTTP with JSON responses and no server-sent event stream. That means each tools/call is one POST that returns one JSON answer. There is no stream to keep open and no partial output to assemble.
Notifications are accepted with 202.
How OneLifeVibe uses it
OneLifeVibe exposes the method at https://onelifevibe.com/mcp and at https://onelifevibe.com/mcp/free. A call looks like this: {"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"olv_list_worlds","arguments":{}}}.
Send it as a POST. The reply is one JSON object on the same id. Call tools/list first to see the tool names and the arguments each one expects.
The free endpoint is a Streamable HTTP MCP server that is stateless and needs no sign-in. It supports initialize, ping, tools/list and tools/call. Both OneLifeVibe connectors behave the same way for tools/call: one request, one response.
Common mistakes
The most common error is putting arguments at the top level of the request instead of inside params.arguments, or leaving out params.name. The server cannot route a call without the tool name.
Another is expecting a stream. With JSON responses there is no event stream, so read the single response body rather than waiting for more data.
Using GET instead of POST, or reusing an id for two calls in flight, causes confusion. Keep one call per POST and match the response id to the request id.
Questions
What is the difference between tools/list and tools/call?
tools/list returns the tools available on the endpoint. tools/call runs one of them by name with an arguments object. Call tools/list first so you use names the server recognizes.
Does the OneLifeVibe MCP endpoint stream results?
No. Both OneLifeVibe connectors use Streamable HTTP with JSON responses and no server-sent event stream. Each tools/call is one POST that returns one JSON answer.
See it working. The OneLifeVibe connector and Platform API put these pieces together.
Written from the OneLifeVibe tool registry and platform configuration, and checked automatically before publishing. Something wrong? Tell us.