Skip to main content
Glama
cmendezs

mcp-einvoicing-de

by cmendezs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

Datev Export

datev_export

Export ZUGFeRD invoice data to DATEV CSV (EXTF 700) for import into DATEV Belegtransfer or Rechnungswesen. Maps line items to booking records with configurable accounts.

Instructions

Export a ZUGFeRD invoice to DATEV CSV format (EXTF 700, Buchungsstapel).

Produces a CSV file importable by DATEV Belegtransfer or DATEV Rechnungswesen. Maps invoice line items to DATEV booking records with configurable accounts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
invoiceYesZUGFeRDInvoice data to export.
client_numberNoDATEV Mandantennummer (client number).1
revenue_accountNoDATEV revenue account number (Erloskonto). Default: 8400 (SKR 03, 19% USt).8400
consultant_numberNoDATEV Beraternummer (consultant number).0
fiscal_year_startNoFiscal year start date (YYYYMMDD). Defaults to Jan 1 of invoice year.
receivable_accountNoDATEV receivable account number (Debitorenkonto). Default: 10000.10000

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv0.11.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / client_number / description
      Added value: +"DATEV Mandantennummer (client number)."
    • addedInput schema / properties / consultant_number / description
      Added value: +"DATEV Beraternummer (consultant number)."
    • addedInput schema / properties / fiscal_year_start / description
      Added value: +"Fiscal year start date (YYYYMMDD). Defaults to\nJan 1 of invoice year."
    • addedInput schema / properties / invoice / additionalProperties
      Added value: +true
    • changedInput schema / properties / invoice / description
      Previous value: -"ZUGFeRDInvoice data."New value: +"ZUGFeRDInvoice data to export."
    • changedInput schema / properties / receivable_account / description
      Previous value: -"DATEV receivable account (Debitorenkonto)."New value: +"DATEV receivable account number\n(Debitorenkonto). Default: 10000."
    • changedInput schema / properties / revenue_account / description
      Previous value: -"DATEV revenue account (Erlöskonto)."New value: +"DATEV revenue account number (Erloskonto).\nDefault: 8400 (SKR 03, 19% USt)."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "type": "object"
+}
  2. Addedv0.6.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses the core transformation ('maps invoice line items to DATEV booking records') and the output ('Produces a CSV file'), but does not explicitly mention side effects, read-only status, permissions, or error conditions. The description does not contradict any annotations.

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

Conciseness5/5

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

The description is two sentences with no fluff. The first sentence front-loads the exact purpose, and the second sentence adds value by explaining the output format and mapping behavior. Every word earns its place.

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

Completeness4/5

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

For a 6-parameter tool with a nested invoice object and an output schema, the description is sufficiently complete: it names the target format, the importing software, and how line items are transformed. Minor gaps such as explicit error handling or read-only status are not critical given the structured metadata that exists.

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 description coverage is 100%, so the schema already fully documents all six parameters. The description adds the phrase 'configurable accounts,' which maps to the account parameters, but it does not meaningfully extend the schema's parameter explanations.

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 opens with a specific verb and resource: 'Export a ZUGFeRD invoice to DATEV CSV format (EXTF 700, Buchungsstapel).' This clearly identifies what the tool does and distinguishes it from generic invoice tools like invoice_convert or invoice_parse.

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 states the output is 'importable by DATEV Belegtransfer or DATEV Rechnungswesen', giving clear context for when an agent should use this tool. However, it does not explicitly compare to alternatives like invoice_convert or state when not to use it.

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

Deploy Server

Other Tools