Skip to main content
Glama
ohneben

Buchhaltungsbutler MCP

by ohneben
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

Transactions: get transactions

transactions_get
Read-onlyIdempotent

Fetch transactions for a customer account using filters like date range, account number, or payer/payee. Supports pagination with limit and offset.

Instructions

🟢 READ-ONLY — Fetches data. Makes no changes to the accounting records. get transactions Get transactions for a specified customer account. The response includes the number of returned rows and an array of transaction datas.

Endpoint: POST /transactions/get

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoA limit of returned data. If no limit is given, the default will be 500. Also the maximum limit is 500. If specified, the field will be validated.
offsetNoThe offset for paging returned data. If no offset is given, the default will be 0. If specified, the field will be validated.
accountNoThe account number of the account the transaction is stored to. If specified, the field will be validated.
api_keyNoOptional. The BB customer api_key to act on. Defaults to the BB_API_KEY configured on the server — only set this to target a different customer.
date_toNoThe transaction's booking date in format 'YYYY-MM-DD' (e.g. '2017-04-26'). All transaction with booking date including and before given value will be returned. An empty string is not considered a valid date.
to_fromNoThe payer/payee of the transaction. If specified, the field will be validated.
date_fromNoThe transaction's booking date in format 'YYYY-MM-DD' (e.g. '2017-04-26'). All transactions with booking date including and after given value will be returned. An empty string is not considered a valid date.
id_by_customer_toNoThe id_by_customer as an integer. All transactions to given value will be returned. The transaction with the given value will NOT be returned! NOTE: By specifying this, the sort changes to id_by_customer ASC, even if you use this in combination with date params. If specified, the field will be validated.
id_by_customer_fromNoThe id_by_customer as an integer. All transactions after given value will be returned. The transaction with the given value will NOT be returned! NOTE: By specifying this, the sort changes to id_by_customer ASC, even if you use this in combination with date params. If specified, the field will be validated.

Tool Definition Quality

B3.4/5.0
Behavior4/5

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

Annotations already indicate read-only, idempotent, and non-destructive behavior. The description reinforces this with 'READ-ONLY' and adds response structure details (number of rows, array of transaction data) and the POST endpoint, providing useful extra context.

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 description is brief and front-loaded with key points. A minor redundancy is repeating 'get transactions' in bold. Overall, every sentence adds value.

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

Completeness3/5

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

Given the lack of output schema and 9 optional parameters, the description covers purpose and safety but omits that an account filter might be necessary despite being optional. The combination with schema is adequate but leaves some uncertainty.

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

Parameters3/5

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

Schema coverage is 100%, so the description carries minimal burden. It mentions 'specified customer account' which aligns with the account parameter but adds no further meaning to other parameters. Adequate but not exceptional.

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 clearly states it retrieves transactions for a specified customer account. However, it does not explicitly differentiate from sibling tools like transactions_get_id_by_customer, making the distinction somewhat implicit.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives such as transactions_add or transactions_get_id_by_customer. The description lacks context for decision-making.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ohneben/Buchhaltungsbutler-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server