Skip to main content
Glama
berthelius

Frihet MCP Server

by berthelius
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

Export DATEV

export_datev
Read-onlyIdempotent

Export accounting data in DATEV EXTF format to import into DATEV Kanzlei-Rechnungswesen. Supports journal entries and accounts receivable/payable master data.

Instructions

Export accounting data in DATEV EXTF format for import into DATEV Kanzlei-Rechnungswesen or compatible systems. Returns a signed download URL valid for 24 hours.

Supported EXTF formats: • extf-buchungsstapel — Journal entries (Buchungsstapel) — most common, use for P&L/tax • extf-debitoren — Accounts receivable master data (Debitoren-/Kreditorenstamm AR) • extf-kreditoren — Accounts payable master data (Debitoren-/Kreditorenstamm AP)

Output encoding is always CP1252 per DATEV EXTF specification. Date range: both periodStart and periodEnd must be ISO 8601 dates (YYYY-MM-DD).

If the DATEV export backend is not deployed for this workspace, returns an honest 'unavailable' response — never a fabricated file URL. / Exporta datos contables en formato DATEV EXTF para importacion en DATEV o sistemas compatibles.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
formatYesDATEV EXTF export format: extf-buchungsstapel (journal entries), extf-debitoren (AR master), extf-kreditoren (AP master) / Formato EXTF de DATEV.
periodEndYesEnd of the export period (ISO 8601 YYYY-MM-DD). Inclusive. / Fin del periodo de exportacion (YYYY-MM-DD). Inclusivo.
periodStartYesStart of the export period (ISO 8601 YYYY-MM-DD). Inclusive. / Inicio del periodo de exportacion (YYYY-MM-DD). Inclusivo.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
fileUrlYesSigned URL to download the DATEV EXTF file
encodingYesFile encoding — always CP1252 per DATEV EXTF spec
filenameYesSuggested filename (e.g. EXTF_Buchungsstapel_2026-01.csv)
rowCountYesNumber of accounting rows in the export
fiscalPeriodYesFiscal period covered (e.g. '2026-01' or '2026-Q1')

Tool Definition Quality

A4.6/5.0
Behavior5/5

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

The description adds significant behavioral context beyond annotations: returns a signed URL valid 24 hours, encoding CP1252, date constraints, and graceful handling when backend unavailable. No contradiction with annotations (readOnlyHint, idempotentHint, etc.).

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 well-structured: purpose sentence, bulleted list of formats, encoding, date rules, and fallback behavior. It is slightly lengthy but every sentence adds value, and key info is front-loaded.

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?

Given output schema exists and 3 parameters fully described, the description covers return type (signed URL, validity), encoding constraints, date formats, and edge case (unavailable backend). It feels complete for the tool's purpose.

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?

Schema coverage is 100%, baseline 3. The description adds value by explaining each format's meaning (journal entries, AR master, AP master) and clarifying date range is inclusive ISO 8601. This goes beyond the schema descriptions.

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 clearly states the tool exports accounting data in DATEV EXTF format, specifies the supported formats, and distinguishes it from sibling tools like einvoice_export by focusing on the DATEV format. The verb 'export' and resource 'accounting data' are specific.

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?

The description gives clear context on when to use this tool (for exporting DATEV-compatible data) but does not explicitly mention when not to use it or compare with alternatives. It implies usage for accounting export needs.

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/berthelius/frihet-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server