Skip to main content
Glama

Get Bookkeeping Transactions

get_bookkeeping_transactions
Read-only

Lists the company's recent transactions in doola Bookkeeping: income, expenses, tax payments, transfers and invoice payments, with amount, date and category. limit caps the rows (1 to 100, default 50). Use it for questions like 'how much did I spend on software'. 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

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_bookkeeping_transactions"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNomax rows (1-100, default 50)
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.
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.
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.5/5.0
Behavior5/5

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

Annotations already establish readOnly/non-destructive/closed-world, and the description adds substantial context beyond them: gating on bookkeepingSetUp, upsell-handling rules for includedInPlan, the nextStep follow-up flow, and the instruction to answer in plain language without exposing field names. This is operational behavior an agent could not infer from the structured fields.

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 and limit semantics are front-loaded, then the set-up/upsell branches follow in a logical order. It is longer than most definitions and the setUpLink/nextStep passage is detailed, but each sentence carries actionable routing or presentation guidance rather than filler.

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?

With no output schema, the description compensates by naming the returned fields and transaction categories, and it covers the degenerate states (no books set up, included in plan) that determine whether calling is even appropriate. Nothing an agent needs to invoke this correctly appears to be missing.

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 the baseline is 3; the description matches the schema restatement of limit (1-100, default 50). It earns above baseline by explaining how companyId should be sourced (from list_companies) and that passing it is preferable to switching the user's active company, which the schema's per-parameter text does not state.

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

Purpose4/5

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

The description uses a specific verb and resource ('Lists the company's recent transactions in doola Bookkeeping') and enumerates the transaction types plus returned fields (amount, date, category), so an agent knows exactly what comes back. It does not explicitly distinguish itself from close siblings like get_bookkeeping_uncategorized_transactions or get_bookkeeping_report, which keeps it from a 5.

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?

It gives a concrete example question ('how much did I spend on software'), covers the bookkeepingSetUp=false case where no books exist, and spells out the includedInPlan=true branch (never offer, share setUpLink, or point to support). It also routes multi-company questions to list_companies with companyId rather than switching active company, which is explicit when-to-use guidance against an alternative.

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.