e-arveldaja MCP Server

Import Wise Transactions

import_wise_transactions

Destructive

Import Wise transaction-history CSV rows into e-arveldaja as bank entries, with dry-run planning, fee handling, and transfer deduplication before execution.

Instructions

Import Wise transaction-history CSV rows. Direct-call contract: DRY RUN by default; execute=true creates rows; each created bank row carries the API type of its true direction (incoming IN → type D, outgoing OUT → type C) and source_direction records that same flow; fees are separate outgoing (type C) transactions; inter-account transfers avoid double-counting confirmed counterpart journals.

Input Schema

TableJSON Schema

Name	Required	Description
`date_to`	No	Only import transactions up to this date (YYYY-MM-DD)
`execute`	No	Actually create transactions (default false = dry run)
`file_ref`	No	Opaque Accounting Inbox Wise CSV reference. Provide exactly one of file_path or file_ref.
`date_from`	No	Only import transactions from this date (YYYY-MM-DD)
`file_path`	No	Absolute path/base64 Wise CSV input. Provide exactly one of file_path or file_ref.
`plan_handle`	No	Execution-plan handle returned by the reviewed dry run. Required for execute=true in addition to approved_command_digest; the digest alone cannot execute.
`skip_jar_transfers`	No	Skip Jar (savings pot) transfers — internal movements within Wise (default true)
`accounts_dimensions_id`	Yes	Bank account dimension ID for the Wise account in e-arveldaja. Must be the dimension of a configured bank account; otherwise refused with wise_dimension_not_bank_account before any write.
`approved_command_digest`	No	Exact lowercase SHA-256 command digest returned by the reviewed dry run. Required for execute=true when mutations are planned.
`fee_account_relation_id`	No	Deprecated alias for fee_account_dimensions_id.
`confirm_own_transfer_ids`	No	Exact Wise IDs explicitly approved as own transfers. TRANSFER-* and BANK_DETAILS_PAYMENT_RETURN-* prefixes are hints only.
`journalized_transfer_ids`	No	Exact { wise_id, journal_id } pairs the operator has checked: the labelled inter-account journal already books that Wise transfer (resolves a wise_transfer_journal_ambiguous review). Each mapping is validated; a rejected one is reported and the row resolves as if unmapped (it may still be skipped as already journalized, or held for review).
`fee_account_dimensions_id`	No	Account dimension ID for the Wise fee expense account.
`acknowledged_journal_holds`	No	Owner-confirmed only: { wise_id, journal_ids } stating those journals do NOT book that held Wise transfer. Releases the row (imported and confirmed normally) only when journal_ids lists every required_acknowledgement_ids journal of its review; never for counterpart, identity or untagged-row holds.
`inter_account_dimension_id`	No	Other bank account dimension ID for inter-account transfers. Auto-detected if only one other bank account exists. Per row, own-account evidence on another bank decides first and this id is the fallback; a row whose counterpart cannot be determined or whose evidence contradicts this id is held (not imported), the other rows are planned.

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv0.29.2Oct 17, 2026

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

changedInput schema / properties / accounts_dimensions_id / description

Previous value: -"Bank account dimension ID for the Wise account in e-arveldaja"New value: +"Bank account dimension ID for the Wise account in e-arveldaja. Must be the dimension of a configured bank account; otherwise refused with wise_dimension_not_bank_account before any write."

addedInput schema / properties / acknowledged_journal_holds

Added value: +{
+  "description": "Owner-confirmed only: { wise_id, journal_ids } stating those journals do NOT book that held Wise transfer. Releases the row (imported and confirmed normally) only when journal_ids lists every required_acknowledgement_ids journal of its review; never for counterpart, identity or untagged-row holds.",
+  "items": {
+    "properties": {
+      "journal_ids": {
+        "items": {
+          "exclusiveMinimum": 0,
+          "maximum": 9007199254740991,
+          "type": "integer"
+        },
+        "minItems": 1,
+        "type": "array"
+      },
+      "wise_id": {
+        "minLength": 1,
+        "type": "string"
+      }
+    },
+    "required": [
+      "wise_id",
+      "journal_ids"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

changedInput schema / properties / inter_account_dimension_id / description

Previous value: -"Other bank account dimension ID for inter-account transfers. Auto-detected if only one other bank account exists; required with 3+ bank accounts."New value: +"Other bank account dimension ID for inter-account transfers. Auto-detected if only one other bank account exists. Per row, own-account evidence on another bank decides first and this id is the fallback; a row whose counterpart cannot be determined or whose evidence contradicts this id is held (not imported), the other rows are planned."

addedInput schema / properties / journalized_transfer_ids

Added value: +{
+  "description": "Exact { wise_id, journal_id } pairs the operator has checked: the labelled inter-account journal already books that Wise transfer (resolves a wise_transfer_journal_ambiguous review). Each mapping is validated; a rejected one is reported and the row resolves as if unmapped (it may still be skipped as already journalized, or held for review).",
+  "items": {
+    "properties": {
+      "journal_id": {
+        "exclusiveMinimum": 0,
+        "maximum": 9007199254740991,
+        "type": "integer"
+      },
+      "wise_id": {
+        "minLength": 1,
+        "type": "string"
+      }
+    },
+    "required": [
+      "wise_id",
+      "journal_id"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

Changed9 schema fields changedv0.25.2Jul 26, 2026

addedInput schema / properties / approved_command_digest

Added value: +{
+  "description": "Exact lowercase SHA-256 command digest returned by the reviewed dry run. Required for execute=true when mutations are planned.",
+  "pattern": "^[0-9a-f]{64}$",
+  "type": "string"
+}

addedInput schema / properties / confirm_own_transfer_ids

Added value: +{
+  "description": "Exact Wise IDs explicitly approved as own transfers. TRANSFER-* and BANK_DETAILS_PAYMENT_RETURN-* prefixes are hints only.",
+  "items": {
+    "minLength": 1,
+    "type": "string"
+  },
+  "type": "array"
+}

changedInput schema / properties / file_path / description

Previous value: -"Absolute path to the regular Wise transaction-history.csv export from Transactions."New value: +"Absolute path/base64 Wise CSV input. Provide exactly one of file_path or file_ref."

addedInput schema / properties / file_ref

Added value: +{
+  "description": "Opaque Accounting Inbox Wise CSV reference. Provide exactly one of file_path or file_ref.",
+  "type": "string"
+}

addedInput schema / properties / inter_account_dimension_id / exclusiveMinimum
```
Added value: +0
```
addedInput schema / properties / inter_account_dimension_id / maximum
```
Added value: +9007199254740991
```
changedInput schema / properties / inter_account_dimension_id / type
```
Previous value: -"number"New value: +"integer"
```

addedInput schema / properties / plan_handle

Added value: +{
+  "description": "Execution-plan handle returned by the reviewed dry run. Required for execute=true in addition to approved_command_digest; the digest alone cannot execute.",
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "file_path",
-  "accounts_dimensions_id"
-]New value: +[
+  "accounts_dimensions_id"
+]

First observedv0.18.1Jul 9, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations declare destructiveHint=true and readOnlyHint=false, so the write nature is already known; the description goes beyond that by disclosing dry-run-by-default behavior, the exact row typing (IN→D, OUT→C), source_direction population, fees as separate type-C rows, and inter-account double-count avoidance. These are meaningful consequences of the call that the annotations do not convey, though nothing is said about failures/partial plans beyond the inter-account clause.

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 dense paragraph front-loaded with the purpose and the dry-run default; every clause earns its place by describing row-typing or counting rules. It is slightly over-packed (direction mapping, fees, and transfers in one run-on) but contains no filler.

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 15-parameter destructive tool with no output schema, the description covers the write semantics well but is silent on what a dry run returns (the plan handle/digest the caller must feed back) and on the reviewed-plan prerequisite workflow. The schema hints at this, but the description leaves the end-to-end call sequence incomplete.

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 parameters like execute, file_ref/file_path, plan_handle, and the dimension IDs are already fully documented. The description reinforces execute semantics and direction mapping but adds no format, default, or interaction detail beyond what the schema states — baseline 3 applies.

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 ('Import Wise transaction-history CSV rows'), which separates it from siblings like process_camt053, import_opening_balances, and reconcile_bank_transactions. An agent can identify the domain and operation from the first sentence.

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 'direct-call contract' explains the dry-run-then-execute flow, which is useful operational context. However, it never states when to prefer this tool over siblings such as process_camt053 or receipt_batch, nor does it mention the prerequisite workflow (reviewing a dry run to get plan_handle) that gates execution.

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

Deploy Server

Import Wise Transactions

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools