Vault Documents
get_vault_documentsCanonical MCP read for vault document inventory. Each document includes its id. On an enrolled financial-workbench connection, an exact own-account documentId lookup may also return a closed sourceVersion with an opaque version token, revision time and extraction-generation marker. Broad inventories and other access scopes omit it; this metadata does not verify source contents, extracted facts or current financial balances. An own-Vault document also carries an X1-authored documentUrl for a direct link; use only that URL, never construct one from an id. On external professional connectors, use get_document_content or get_document_download_url once per document id when those tools are mounted. They require current download permission and household connected-document access, are rate limited, and record each release in household access history. Otherwise open the document in X1. On your own vault each document also carries summary, X1's one-line reading of it (null on a client's documents). Advisors and scoped specialists receive explicitly shared documents plus active visible coordination-thread attachments, while managed-program roles see metadata according to their assignment scope.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "get_vault_documents"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max results (default 50) | |
| category | No | Filter by category | |
| clientId | No | Client or member user ID | |
| documentId | No | Optional document ID to poll one document's current indexing state. |