Get Bookkeeping Report
get_bookkeeping_reportGenerates one of the company's financial statements from doola Bookkeeping. reportType is PROFIT_AND_LOSS (profit and loss, income statement), BALANCE_SHEET, CASH_FLOW_INDIRECT (cash flow statement), EXPENSES_BY_CATEGORY (spending per expense category) or TRIAL_BALANCE (general ledger). exportType PDF or XLSX returns url, a link to download the file: give it to the user as a download link named after fileName, exactly as returned, never open or fetch it yourself, and call again for a new one instead of reusing an old link. exportType JSON returns the figures themselves, for totals or a chart. grouping is DAILY, MONTHLY, QUARTERLY or YEARLY, and beginDate and endDate are YYYY-MM-DD. When bookkeepingSetUp is false there are no books to read yet. If includedInPlan is true, bookkeeping is already in the user's doola plan: never offer it, share setUpLink where they set it up, or with no setUpLink point them to doola support. Otherwise follow nextStep to offer doola Bookkeeping. Answer in plain language and never show the user the field names. It reads the active company; for another company the user owns, pass its companyId from list_companies instead of switching the active company.
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": {
"exportType": "<exportType>",
"grouping": "<grouping>",
"beginDate": "<beginDate>",
"endDate": "<endDate>",
"reportType": "<reportType>"
},
"name": "get_bookkeeping_report"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| context | No | Optional, for analytics only. In one sentence, why you are calling this tool and how it serves the user's goal. Describe the purpose in general terms: never include names, emails, phone numbers, addresses, IDs or any other personal details. | |
| endDate | Yes | end date YYYY-MM-DD | |
| grouping | Yes | grouping — one of DAILY, MONTHLY, QUARTERLY, YEARLY | |
| beginDate | Yes | begin date YYYY-MM-DD | |
| companyId | No | OPTIONAL. The doolaCompanyId (an id like '30E5c1AQA326uOuDlsic4No7zZ5'). LEAVE THIS EMPTY/UNSET to use the customer's currently active company — that is the correct default for almost every question. Pass a value ONLY when the customer explicitly references a *different* company they own (e.g. 'show me transactions for my other company X'). NEVER pass a company name, slug, or human label here — only an exact id string. | |
| llm_model | No | Optional, for analytics only. Your exact model identifier from your system prompt (e.g. "claude-opus-4-8"), or "unknown" if unsure. Never guess. | |
| exportType | Yes | export type — one of XLSX, PDF, JSON | |
| reportType | Yes | report type — one of PROFIT_AND_LOSS, BALANCE_SHEET, CASH_FLOW_INDIRECT, EXPENSES_BY_CATEGORY, TRIAL_BALANCE | |
| conversation_id | No | Optional, for analytics only. The exact conversation_id from this server's previous response, unchanged. The first response provides one, so leave this out until you have it and never invent one. Keep passing the same value for the rest of the conversation, even when the user moves on to a new request. |