JSON-RPC method
tools/list
List the tools your key can call; there is no pagination.
Returns the 20 plungeai_* tools in catalog order, or only the tools your key is fenced to. Support: supported; there is no pagination, so no nextCursor comes back and a cursor param is ignored.
Params
| Param | Type | Required | Description |
|---|---|---|---|
cursor | string | no | Ignored: the full list comes back every time |
Result
| Field | Value |
|---|---|
tools[] | One entry per tool: name, description and inputSchema (JSON Schema) |
tools[].annotations | { "readOnlyHint": true } on the six read-only tools; the other 14 carry no annotations |
tools[].outputSchema | On seven tools: the outcome envelope on six, the status object on plungeai_get_workflow_status |
Example
curl -s https://mcp.plungeai.com/v1 \
-H "Authorization: Bearer $PLUNGE_API_KEY" \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":2,"method":"tools/list"}'{"jsonrpc":"2.0","id":2,"result":{"tools":[{"name":"plungeai_whoami","description":"…","inputSchema":{"type":"object","properties":{"user_request":{"type":"string"},"format":{"type":"string","enum":["markdown","json"]}}},"annotations":{"readOnlyHint":true}}]}}The response above is abridged to one of the 20 entries, and its description string is shortened to …. The exact schemas are in /mcp-tools.json and on each tool page.
Errors
Protocol errors mean the request never reached a tool; the body is {"jsonrpc":"2.0","error":{"code":…,"message":"…"},"id":…}.
| HTTP | Code | When |
|---|---|---|
| 401 | -32001 | No key, or a wrong, revoked or expired key, or a bearer that does not start with ozk_ |
The full table is on the MCP Reference overview.