e-arveldaja MCP Server

Receipt Batch

receipt_batch

Destructive

Scan receipt files in e-arveldaja, preview bank matches and accounting entries, then create records after explicit approval.

Instructions

Merged receipt batch. scan inspects files; dry_run previews; create/create_and_confirm require explicit approval.

Input Schema

TableJSON Schema

Name	Required	Description
`mode`	No	Workflow phase to run. Defaults to scan.
`detail`	No	Per-file results detail. Default compact omits the OCR raw_text and field_provenance; full keeps them.
`date_to`	No	Optional receipt file modified-date upper bound (YYYY-MM-DD). Filters which receipt FILES are scanned; does not affect bank transactions.
`file_ref`	No	Opaque Accounting Inbox receipt-folder reference.
`date_from`	No	Optional receipt file modified-date lower bound (YYYY-MM-DD). Filters which receipt FILES are scanned; does not affect bank transactions.
`file_types`	No	Optional file type filter for scan mode
`folder_path`	No	Folder path with receipts. Provide exactly one of folder_path or file_ref.
`plan_handle`	No	Consume-once handle from dry_run (plan_handles.create / .create_and_confirm). REQUIRED for create/create_and_confirm.
`approved_manifest`	No	Exact manifest returned by dry_run; required for create/create_and_confirm.
`transaction_date_to`	No	Optional bank accounting-date upper bound for auto-matching (YYYY-MM-DD). Independent of the receipt file date_to.
`transaction_date_from`	No	Optional bank accounting-date lower bound for auto-matching (YYYY-MM-DD). Independent of the receipt file date_from.
`accounts_dimensions_id`	No	Bank account dimension ID used when matching bank transactions. Required except in scan mode.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.29.2Oct 17, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / detail

Added value: +{
+  "description": "Per-file results detail. Default compact omits the OCR raw_text and field_provenance; full keeps them.",
+  "enum": [
+    "compact",
+    "full"
+  ],
+  "type": "string"
+}

Changed9 schema fields changedv0.25.2Jul 26, 2026

addedInput schema / properties / approved_manifest

Added value: +{
+  "description": "Exact manifest returned by dry_run; required for create/create_and_confirm.",
+  "items": {
+    "anyOf": [
+      {
+        "properties": {
+          "relative_path": {
+            "minLength": 1,
+            "type": "string"
+          },
+          "sha256": {
+            "pattern": "^[0-9a-f]{64}$",
+            "type": "string"
+          }
+        },
+        "required": [
+          "relative_path",
+          "sha256"
+        ],
+        "type": "object"
+      },
+      {
+        "properties": {
+          "display_name": {
+            "type": "string"
+          },
+          "file_ref": {
+            "pattern": "^[A-Za-z0-9_-]{43}$",
+            "type": "string"
+          },
+          "sha256": {
+            "pattern": "^[0-9a-f]{64}$",
+            "type": "string"
+          }
+        },
+        "required": [
+          "file_ref",
+          "sha256"
+        ],
+        "type": "object"
+      }
+    ]
+  },
+  "type": "array"
+}

changedInput schema / properties / date_from / description

Previous value: -"Optional receipt modified-date lower bound (YYYY-MM-DD)"New value: +"Optional receipt file modified-date lower bound (YYYY-MM-DD). Filters which receipt FILES are scanned; does not affect bank transactions."

changedInput schema / properties / date_to / description

Previous value: -"Optional receipt modified-date upper bound (YYYY-MM-DD)"New value: +"Optional receipt file modified-date upper bound (YYYY-MM-DD). Filters which receipt FILES are scanned; does not affect bank transactions."

addedInput schema / properties / file_ref

Added value: +{
+  "description": "Opaque Accounting Inbox receipt-folder reference.",
+  "type": "string"
+}

changedInput schema / properties / folder_path / description

Previous value: -"Folder path with receipts"New value: +"Folder path with receipts. Provide exactly one of folder_path or file_ref."

addedInput schema / properties / plan_handle

Added value: +{
+  "description": "Consume-once handle from dry_run (plan_handles.create / .create_and_confirm). REQUIRED for create/create_and_confirm.",
+  "type": "string"
+}

addedInput schema / properties / transaction_date_from

Added value: +{
+  "description": "Optional bank accounting-date lower bound for auto-matching (YYYY-MM-DD). Independent of the receipt file date_from.",
+  "type": "string"
+}

addedInput schema / properties / transaction_date_to

Added value: +{
+  "description": "Optional bank accounting-date upper bound for auto-matching (YYYY-MM-DD). Independent of the receipt file date_to.",
+  "type": "string"
+}

removedInput schema / required
```
Removed value: -[
-  "folder_path"
-]
```

First observedv0.18.1Jul 9, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and non-idempotency, so the safety profile is covered structurally. The description adds genuinely new behavioral context: create modes require explicit approval, which tells the agent this is a gated, human-confirmed mutation rather than an automatic write.

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 sentence split into mode clauses, front-loaded and free of filler. The opening fragment 'Merged receipt batch' is the weakest part but the rest is dense and readable.

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

Completeness3/5

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

For a 12-parameter, zero-required, multi-phase workflow with no output schema, the description is thinner than ideal: it never explains the scan -> dry_run -> approve -> create handoff, what a plan_handle represents, or how the auto-matching transaction dates relate to the run. The rich schema compensates for most parameter gaps, keeping this at minimum-viable rather than inadequate.

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% with 12 parameters, each carrying its own description (including mode defaults and the folder_path/file_ref exclusivity). The description's mode clause largely restates what the enum descriptions already say, so the baseline of 3 applies.

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 mode breakdown gives concrete verbs (inspects, previews, create) over the receipt-file resource, so an agent can infer this tool scans a receipt folder and drafts/creates accounting records from it. The lead phrase 'Merged receipt batch' is noun-only and cryptic, and nothing distinguishes it from siblings like accounting_inbox or continue_accounting_workflow, so it stops short of a 5.

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

Usage Guidelines3/5

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

The ordering scan -> dry_run -> create/create_and_confirm is implied by the mode list, and 'require explicit approval' hints at a gated final phase. But there is no explicit when-to-use / when-not-to-use guidance and no pointer to the obvious sibling alternatives (accounting_inbox, continue_accounting_workflow, process_camt053) that handle adjacent inbox workflows.

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

Deploy Server

Receipt Batch

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools