Buchhaltungsbutler MCP

Settings: get creditors

creditors_list

Read-onlyIdempotent

List all creditors/suppliers from your accounting records to resolve a supplier name to the creditor ID required by receipt and posting tools.

Instructions

🟢 READ-ONLY: Fetches data. Makes no changes to the accounting records.

get creditors

Get all creditors

Use to list suppliers, for example to resolve a supplier name to the creditor id the receipt and posting tools expect.

For customers you invoice, use debtors_list.

Supports limit and offset. Do not assume rows is the grand total. Continue paging until empty and check progress. v1 offers no delete endpoint for creditors, so they can only be created, listed and updated.

Endpoint: POST /settings/get/creditors

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	limit of the results, default is 25 results
`offset`	No	offset of the results, default is 0

Output Schema

TableJSON Schema

Name	Required	Description
`data`	No	An array of creditors
`rows`	No	Number of returned rows
`message`	No	blank
`success`	Yes	Success boolean

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.1.3Sep 26, 2026
- changedOutput schema / properties / data / items / properties / email / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / data / items / properties / uid_ch / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
Addedv1.1.2Sep 15, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already mark readOnly, idempotent, and non-destructive; the description reinforces this in plain language and adds non-obvious behavior: response rows may not be a grand total, continue paging until empty, and no delete endpoint exists for creditors in v1. No annotation contradiction.

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?

Mostly tight and front-loaded with read-only status and main purpose. There is slight redundancy between the 'get creditors' heading and 'Get all creditors' sentence, but the extra context (debtors alternative, paging, delete limitation) justifies the length.

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 simple list tool, the description covers purpose, alternative, pagination behavior, and API lifecycle constraints. Since an output schema exists, return-value detail is not needed.

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?

The schema already describes limit/offset with defaults, so baseline is 3. The description adds value by explaining these are paging controls and warning not to treat a single response as complete, which is beyond raw schema.

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?

The description uses a specific verb ('list'/'get') with resource 'creditors' and clarifies they are suppliers. It explicitly differentiates from debtors_list, so an agent can select this over the most similar sibling without inspecting schemas.

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 states a concrete use case (resolving a supplier name to creditor id for receipt and posting tools) and directs customers to debtors_list. It also gives paging loop guidance, which is when-to-keep-calling context.

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

Deploy Server