kb_get_document
Read a stored knowledge base document's full content and metadata, page by page, instead of search chunks. Use when you need a known or previously written document read end to end.
Instructions
Read a KB document's stored content and metadata (not just search chunks). Use when the user wants a known document, or a previously written one, read end to end.
Content comes in pages of up to 40,000 characters as sent (JSON-escaped, so quotes and line breaks
count twice): `truncated` is true and `next_cursor` is set
while more follows; pass it back as `cursor` for the next page. A whole-file kb_search result's
`content_next_cursor` is such a cursor too. `total_chars` is the full length.
For a file, `document.content_hash` fingerprints the full stored text: it is the same on every page
while the document is unchanged, and propose_context_record cites the document with it.
`document.text_fingerprint` fingerprints the same text with spacing, quote marks and case
normalised, the way the context_write_qa skill compares a copy of it. A long
name or error ends in "…"; a value too large to return (metadata, path, source_url) is null and
`document.omitted_fields` names it with its size.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": {
"project_id": "<project_id>",
"document_id": "<document_id>"
},
"name": "kb_get_document"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| cursor | No | ||
| project_id | Yes | ||
| document_id | Yes |