Skip to main content
Glama

generate_datev_csv

Read-onlyIdempotent

Generate German DATEV EXTF v700 Buchungsstapel CSV files for SKR03/SKR04 accounting imports from booking entries, producing DATEV-ready import batches.

Instructions

Generate German DATEV EXTF v700 Buchungsstapel CSV (SKR03 / SKR04) accounting import batches via Apify Cloud.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "entries": "<entries>"
    },
    "name": "generate_datev_csv"
  }
}

Input Schema

NameRequiredDescriptionDefault
entriesYesAccounting bookings to serialize into DATEV EXTF CSV rows.
client_numberNoDATEV Mandantennummer (1 to 5 digits).
chart_of_accountsNoGerman DATEV standard chart of accounts.SKR03
consultant_numberNoDATEV Beraternummer (4 to 7 digits).
fiscal_year_startNoFiscal year start date in YYYYMMDD format.20260101

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so safety behavior is covered. The phrase 'via Apify Cloud' usefully confirms an external cloud execution path consistent with openWorldHint, but the description says nothing about cost/credits, latency, auth requirements, or whether output is returned inline versus stored externally.

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?

A single front-loaded sentence with no filler and the key qualifiers (German, EXTF v700, SKR03/SKR04) placed early. It is efficient, though arguably undersized for a tool with a nested entry array and DATEV-specific domain rules.

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?

The tool serializes nested booking entries into a strict accounting format with no output schema, yet the description never says what is returned or where the CSV lands (inline content, file, Apify key-value store). For a domain-complex, cloud-executed generator this leaves a critical operational gap despite the strong parameter schema.

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% and every parameter carries a description, including the SKR03/SKR04 enum and DATEV-specific fields like Gegenkonto and Mandantennummer. The description only restates the chart-of-accounts options already present in the schema, adding no format-level meaning such as how booking rows map to EXTF columns.

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 gives a specific verb ('Generate') and a precisely named resource ('German DATEV EXTF v700 Buchungsstapel CSV', SKR03/SKR04), which makes it unambiguous against the country/format-specific siblings such as generate_sepa_xml or generate_uk_bacs_file. It stops short of an explicit differentiator sentence, but the format naming does the disambiguation work.

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?

There is no when-to-use, when-not-to-use, or alternative-selection guidance, and no stated prerequisites (Apify account/API token, valid DATEV consultant/client numbers). The only usage signal is implicit in the purpose statement, so an agent must infer everything else.

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