Skip to content

Free, Open Source, Self-Hosted WhatsApp API Gateway

docs(api): call a real tool in the MCP request example

Yudhi Armyndharisa77b2f5841ee
diff --git a/docs/06-api-specification.md b/docs/06-api-specification.md
index 03a0410a1..7b3a7ed72 100644
--- a/docs/06-api-specification.md
+++ b/docs/06-api-specification.md
@@ -6331,19 +6331,21 @@ Key facts:
"id": 3,
"method": "tools/call",
"params": {
- "name": "session_send_text",
- "arguments": { "sessionId": "default", "to": "6281234567890", "text": "Hello from MCP" }
+ "name": "MessageSendText",
+ "arguments": { "sessionId": "default", "chatId": "[email protected]", "text": "Hello from MCP" }
}
}
```
+`MessageSendText` is a write tool: it is listed only with `MCP_READONLY=false` and needs an `OPERATOR` key.
+
**Response** `200` — `text/event-stream`; the `data:` line of its `event: message` frame is this JSON-RPC 2.0 envelope
```json
{
"jsonrpc": "2.0",
"id": 3,
- "result": { "content": [{ "type": "text", "text": "{\"success\":true,\"messageId\":\"…\"}" }] }
+ "result": { "content": [{ "type": "text", "text": "{\"messageId\":\"…\",\"timestamp\":1719312000}" }] }
}
```