Docsbook agent reply
docsbook_agent_replyWRITE$0.008 / callAnswer the Docsbook agent's question, or add something to a job it is already working on — the decision it asked for, the fact it could not find, a correction. It picks the job back up with the whole exchange in front of it. Only for a job that is still open; a finished one is finished, start a new one with docsbook_agent.
The job to reply to.
What you want to tell the agent, in your own words.
Call it#
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "docsbook_agent_reply",
"arguments": {
"task_id": "<task_id>",
"text": "<text>"
}
}
}curl -X POST 'https://docsbook.io/api/mcp/server' \
-H 'Authorization: Bearer dbk_YOUR_API_KEY' \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"docsbook_agent_reply","arguments":{"task_id":"<task_id>","text":"<text>"}}}'Try it over REST#
The same tool is callable as a plain HTTP request, no MCP client required. It runs on the same server, at the same price.
/api/v1/tools/docsbook_agent_replyYour API key, sent as Authorization: Bearer dbk_YOUR_API_KEY.Sent as the Authorization header. Your key is used only by your browser for this request — it is never sent to Docsbook or stored.
The arguments above, as one JSON object.
curl -X POST 'https://docsbook.io/api/v1/tools/docsbook_agent_reply' \
-H 'Authorization: Bearer dbk_YOUR_API_KEY' \
-H 'Content-Type: application/json' \
-d '{"args":{"task_id":"<task_id>","text":"<text>"}}'