Skip to main content
Glama

MaxRechnung

DATEV-Stammdaten der Personenkonten (Debitoren und Kreditoren)

export_datev_creditors
Read-only

Tarif: ab Business (darunter antwortet die API mit plan_required).

DATEV-Stammdaten der Personenkonten (Debitoren und Kreditoren)

Stammdaten im DATEV-Format (EXTF, Kategorie 16 „Debitoren/Kreditoren“, Formatversion 5, 254 Spalten, CP1252, Dateiname EXTF_Debitoren_Kreditoren_…csv): Sammel-Debitor und Sammel-Kreditor mit Namen; je Kunde der ausgestellten Rechnungen sein Debitor — Sammel-Debitor aus den Kanzlei-Stammdaten plus laufende Nummer, die sich nie ändert (10001, 10002 …) — mit Name, USt-IdNr., Anschrift und E-Mail aus der jüngsten Rechnung (Kunde = Kundennummer, sonst USt-IdNr., sonst Name); je Lieferant im Eingang (ohne ignorierte, eigene und Fremdwährungsbelege) sein Kreditor — Sammel-Kreditor plus laufende Nummer (70001, 70002 …) — mit Name, Kurzbezeichnung, USt-IdNr., Steuernummer, Anschrift, E-Mail und IBAN aus dem jüngsten Beleg (Lieferant = USt-IdNr., sonst Steuernummer, sonst Name). Ist eine Art in den Stammdaten ausgeschaltet, fehlen ihre Einzelkonten. Die Kanzlei importiert die Datei vor dem ersten Buchungsstapel. Scope datev:read, Limit wie GET /exports/datev.

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": "export_datev_creditors"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare read-only and non-destructive behavior, and the description adds substantial context beyond them: plan_required below Business, exact EXTF format, 254 columns, CP1252 encoding, filename pattern, account numbering, matching logic, inclusion/exclusion rules, and missing-account behavior.

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 dense but most detail is functionally relevant to the DATEV export format and content rules. The repeated title and the very long, multi-clause sentence slightly reduce readability and front-loading.

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 available, the description still supplies the file format, encoding, filename, account-generation rules, exclusions, tariff behavior, and scope needed to understand what the export produces. It is complete for this complex export tool.

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 tool has no parameters, so the baseline is 4. The description does not need to compensate for schema gaps, and it correctly focuses on output/data semantics instead.

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 identifies the resource precisely: DATEV master data for debtor and creditor personal accounts in EXTF category 16, with specific content rules. It never uses an explicit export/generate verb and does not directly contrast itself with the sibling export_datev, so it is clear but not maximally differentiated.

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

Usage Guidelines4/5

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

It gives useful operational context: available from the Business plan, requires datev:read, and the file is imported before the first posting batch. It does not explain when to choose this over export_datev or other DATEV-related exports, so exclusions and alternatives are missing.

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.

Resources