Skip to main content
Glama

Get Bookkeeping Report

get_bookkeeping_report
Read-only

Generates 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

NameRequiredDescriptionDefault
contextNoOptional, 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.
endDateYesend date YYYY-MM-DD
groupingYesgrouping — one of DAILY, MONTHLY, QUARTERLY, YEARLY
beginDateYesbegin date YYYY-MM-DD
companyIdNoOPTIONAL. 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_modelNoOptional, for analytics only. Your exact model identifier from your system prompt (e.g. "claude-opus-4-8"), or "unknown" if unsure. Never guess.
exportTypeYesexport type — one of XLSX, PDF, JSON
reportTypeYesreport type — one of PROFIT_AND_LOSS, BALANCE_SHEET, CASH_FLOW_INDIRECT, EXPENSES_BY_CATEGORY, TRIAL_BALANCE
conversation_idNoOptional, 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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the readOnlyHint/destructiveHint annotations, the description discloses non-obvious workflow behavior: links must be handed to the user verbatim, never fetched, and never reused (call again instead). It also explains state gating (no books exist when bookkeepingSetUp is false) and a commercial rule (never offer bookkeeping when includedInPlan is true), none of which the annotations convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded and nearly every clause carries operational weight, but the sentence restating grouping values and the beginDate/endDate format duplicates the schema verbatim, and the whole thing is one dense block rather than being broken into distinct guidance points.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 9-parameter, no-output-schema tool with several conditional branches, the description covers report selection, export handling, plan/setup gating, company scoping, and how to phrase the answer to the user. An agent has enough to call it correctly and handle every documented edge case without further inference.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds meaning the schema lacks: what each reportType actually contains (income statement, general ledger, spending per category), that exportType PDF/XLSX yields a url while JSON yields figures, and the YYYY-MM-DD date format. It does not add anything about companyId or the analytics-only parameters, which the schema already handles well.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Generates one of the company's financial statements from doola Bookkeeping") and enumerates every report type with a plain-language gloss, so an agent can distinguish it from siblings like get_bookkeeping_transactions or get_bookkeeping_vendors without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit branching: use JSON when the user wants totals or a chart, PDF/XLSX when they want a downloadable file, and pass companyId only when the user references a different company they own. It also names the correct fallback paths for bookkeepingSetUp=false, includedInPlan=true, and nextStep, so there is no ambiguity about which case applies.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.