Conecto

Export the books

books_export

A file in the file store, with a download link: journal (a CSV of every line of every entry from-to, for an accountant or another program), accounts (the chart with balances on to) or datev (a DATEV Buchungsstapel for a German tax adviser: one fiscal year, from-to, default the year so far; needs the datev settings once) or fec (the French Fichier des Écritures Comptables for a tax audit: the fiscal year that holds to, every entry; needs the fec settings once). Conecto files no tax returns: for UK VAT (Making Tax Digital) the journal CSV is the digital link into bridging software. Costs $0.001 per call; nothing if it fails.

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": {
      "what": "<what>"
    },
    "name": "books_export"
  }
}

Input Schema

Name	Required	Description
`to`	No	YYYY-MM-DD
`fec`	No	For what: fec, kept for the next export. siren (9 digits; read from a French VAT ID when left out); accounts: each account code used to its plan comptable général number, like {"4000": "706000", "1010": "512000"} (same_numbers: true when the chart already uses them).
`from`	No	YYYY-MM-DD
`what`	Yes
`datev`	No	For what: datev, kept for the next export. adviser (Beraternummer) and client (Mandantennummer) from the tax adviser; chart "03" (SKR03) or "04" (SKR04); account_length (4 to 8, default 4); accounts: each account code used to its DATEV number, like {"4000": "8400", "1010": "1200"} (same_numbers: true when the chart already uses them; books set up on the skr03 or skr04 chart do, and need neither chart nor accounts here); tax_keys: a tax's BU-Schlüssel when it isn't German VAT at 19 or 7 percent.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 9, 2026

changedInput schema / properties / datev / description

Previous value: -"For what: datev, kept for the next export. adviser (Beraternummer) and client (Mandantennummer) from the tax adviser; chart \"03\" (SKR03) or \"04\" (SKR04); account_length (4 to 8, default 4); accounts: each account code used to its DATEV number, like {\"4000\": \"8400\", \"1010\": \"1200\"} (same_numbers: true when the chart already uses them); tax_keys: a tax's BU-Schlüssel when it isn't German VAT at 19 or 7 percent."New value: +"For what: datev, kept for the next export. adviser (Beraternummer) and client (Mandantennummer) from the tax adviser; chart \"03\" (SKR03) or \"04\" (SKR04); account_length (4 to 8, default 4); accounts: each account code used to its DATEV number, like {\"4000\": \"8400\", \"1010\": \"1200\"} (same_numbers: true when the chart already uses them; books set up on the skr03 or skr04 chart do, and need neither chart nor accounts here); tax_keys: a tax's BU-Schlüssel when it isn't German VAT at 19 or 7 percent."

First observedOct 28, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations only say readOnly=false, idempotent=false, destructive=false; the description adds substantive behavior beyond that: the result is a file in the file store with a download link, pricing ($0.001 per call, nothing if it fails), that datev/fec settings are stored and reused ('needs the datev settings once'), and the default fiscal-year scoping for datev. These are exactly the operational facts an agent needs before spending money on a call.

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

Conciseness3/5

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

One dense run-on paragraph with layered parentheses (four export types, two settings pointers, a tax disclaimer, and pricing all in a single block), which makes it harder to scan than a short bulleted breakdown would be. The lead clause is front-loaded, but the middle of the sentence is heavy going.

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 five-parameter tool with nested objects and no output schema, the description covers the return artifact (file plus download link), cost, persistence of datev/fec configuration, and per-variant scope. The remaining thin spot is default from/to handling for the journal and accounts exports, which the description leaves implicit.

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 already 80% and the nested datev/fec objects carry their own field descriptions, so baseline is high; the description still adds meaning by mapping from/to differently per 'what' (journal spans from-to, datev is one fiscal year with a default, fec is the fiscal year containing 'to'). It does not clarify default behavior for from/to on journal or accounts, leaving one gap.

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?

States a specific verb and resource ('Export the books') and immediately enumerates the four concrete outputs (journal CSV, accounts chart, DATEV Buchungsstapel, FEC), each with a one-line characterization of what the artifact is. An agent can tell this apart from the sibling save/list/report tools without opening the schema.

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?

Gives per-variant selection guidance tied to the consumer: journal for an accountant or another program, datev for a German tax adviser, fec for a French tax audit, and explicitly notes 'Conecto files no tax returns' with the UK VAT/Making Tax Digital journal-CSV workaround. It does not name sibling tools (e.g. account_export_all) or state when not to use this export, so it stops short of full alternative routing.

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

All Conecto tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?