Read a long result in parts
read_resultRead a long page of a result in parts, from where its reply cut it short.
Also reads a search_companies list that was cut to fit: that has one page, page=0,
and no other page exists for it.
Use the request_id, page and next_offset that a summary, a cut page or the
previous part gave, and keep calling with the next_offset each part returns until
eof is true — and stop as soon as you have what you need rather than reading the
whole page by reflex. Reading runs no new scrape: the page comes from disk where this
server wrote it, or from the API, which keeps the results of queued requests. Returns
text plus offset, returned_chars, total_chars, next_offset and eof.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"request_id": "<request_id>"
},
"name": "read_result"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Which page of the result, counting from 0. Most results have one; a request for several pages of results, a search say, has more. A `search_companies` list is always page 0. | |
| length | No | Most characters to return; fewer come back if they would not fit. | |
| offset | No | Character to start at: the `next_offset` a summary, a cut page or the previous part gave. | |
| request_id | Yes | The `request_id` of the result to read. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||