Skip to main content
Glama
ohneben

Buchhaltungsbutler MCP

by ohneben

Postings: add free posting

postings_add_free

Add a free posting to the accounting system by specifying date, description, amount, debit and credit accounts, and VAT rate. Record journal entries directly.

Instructions

🟡 WRITE · creates data — Creates new records (receipts, transactions, postings, invoices, master data). Not idempotent — calling twice may create duplicates. add free posting Add a free posting.

Endpoint: POST /postings/add/free

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
vatYesThe vat rate of the posting. Possible vats: - 0_none ('keine Ust.') - 19_vat ('19% Ust.') - 7_vat ('7% Ust.') - 19_pre ('19% Vst.') - 7_pre ('7% Vst.') - 19_both_1 ('§13b 19% USt./VSt.') - 19_both_2 ('I.g.E. 19% USt./VSt.') - 7_both ('I.g.E. 7% USt./VSt.') - 19_both_1_no_pre ('§13b 19/16% USt.') - 19_both_2_no_pre ('i.g.E. 19/16% USt.') - 7_both_no_pre ('i.g.E. 7/5% USt.') - 19_pre_app ('19/16% Aufz. VSt.') - 7_pre_app ('7/5% Aufz. VSt.') - 19_both_app_1 ('§13b 19/16% USt./Aufz. VSt.') - 19_both_app_2 ('i.g.E. 19/16% USt./Aufz. VSt.') - 7_both_app ('i.g.E. 7/5% USt./Aufz. VSt.')
dateYesThe date of the posting.
amountYesThe amount of the posting.
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.
postingtextYesThe description of the posting.
cost_locationNoThe cost location number. If specified, field will be validated.
cost_location_twoNoThe cost location two number. If specified, field will be validated.
postingaccount_debitYesThe debit account number of the posting.
postingaccount_creditYesThe credit account number of the posting.
Behavior4/5

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

The description includes a warning that the tool creates data and is not idempotent, which is useful beyond the annotations. It aligns with the annotations (readOnlyHint=false, idempotentHint=false). However, it does not describe side effects like validation of cost_location fields or potential error conditions.

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

Conciseness3/5

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

The description is short but includes a generic template line ('🟡 WRITE ...') that may be repeated across tools, adding noise. The title is effectively repeated in the description. It could be more streamlined.

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

Completeness2/5

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

For a tool with 9 parameters (6 required) and many siblings, the description is too sparse. It does not explain what the tool returns, how to interpret results, or how it differs from similar posting tools. The absence of an output schema increases the need for descriptive completeness.

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?

The input schema covers all parameters with detailed descriptions (100% coverage). The tool description itself adds no parameter-specific information beyond the schema, so the baseline of 3 is appropriate.

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 title 'Postings: add free posting' and the description 'Add a free posting.' clearly state the action and resource. However, the description does not differentiate this tool from siblings like 'postings_add_batch_free' or 'postings_add_receipt', which could cause confusion.

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?

The description provides no guidance on when to use this tool versus its alternatives. There is no mention of prerequisites, contextual suggestions, or scenarios where other tools (e.g., 'postings_add_batch_free') would be more appropriate.

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