Glossary
tools/list
tools/list is the MCP method that returns the tools a server offers, each with its input schema.
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.
- Each OneLifeVibe tool publishes its inputSchema in tools/list (connectors) and GET /api/platform/v1/tools (Platform API). Schemas set additionalProperties: false.
- 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/list is defined by the Model Context Protocol specification. It is the method a caller uses to discover what a server can do. The response lists the server's tools and includes an input schema for each one.
The schema is the practical part. It describes the arguments a tool accepts, so your code can build a valid tools/call request instead of guessing at field names or types. A tool that appears in tools/list is the unit you call. The list is how you find it.
How it works
Over MCP, tools/list is a JSON-RPC request. You send the method name and read the result: the available tools plus their inputSchema entries. Your client can cache the result, but it should treat the list as server-owned data rather than a fixed contract you hardcode.
When a tool takes structured input, the inputSchema defines the allowed properties. Read it before tools/call. If a request fails, compare what you sent with the schema first. The schema is the source of truth for field names and types.
How OneLifeVibe uses it
OneLifeVibe exposes tools/list on its connector MCP server. Each OneLifeVibe tool publishes its inputSchema in tools/list for connectors and at GET /api/platform/v1/tools for the Platform API. OneLifeVibe schemas set additionalProperties: false, which means the schema does not allow extra properties. Send only the fields defined in inputSchema.
The server at https://onelifevibe.com/mcp/free is a Streamable HTTP MCP server with JSON responses. It is stateless and requires no sign-in. Its methods are initialize, ping, tools/list and tools/call. On OneLifeVibe connectors, resources/list and prompts/list answer with empty lists, and notifications are accepted with 202. Use tools/list to discover the callable tools, then tools/call to invoke one.
Common mistakes
A common mistake is hardcoding a tool list. Call tools/list and read the current result. Another is ignoring inputSchema and sending extra fields. Because OneLifeVibe schemas set additionalProperties: false, extra properties are outside the schema. Build requests from the published schema.
Do not confuse tools/list with tools/call. The first returns tool definitions and schemas. The second invokes a tool. Also expect resources/list and prompts/list to return empty lists on OneLifeVibe connectors, and treat a 202 for a notification as acceptance rather than as a tool result.
Questions
What does tools/list return?
It returns the tools a server offers, each with its input schema. Use that schema to build a valid tools/call request.
How do I inspect OneLifeVibe tool schemas from the Platform API?
Send GET /api/platform/v1/tools. Each OneLifeVibe tool publishes its inputSchema there and in tools/list for connectors.
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.