Skip to main content
Glama
e-arveldaja MCP Server

e-arveldaja MCP Server

by iseppo

Import Wise Transactions

import_wise_transactions
Destructive

Import Wise transaction-history CSV rows into e-arveldaja with a dry run by default; execute to create bank transactions, separate fees, and avoid double-counting transfers.

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

NameRequiredDescriptionDefault
date_toNoOnly import transactions up to this date (YYYY-MM-DD)
executeNoActually create transactions (default false = dry run)
file_refNoOpaque Accounting Inbox Wise CSV reference. Provide exactly one of file_path or file_ref.
date_fromNoOnly import transactions from this date (YYYY-MM-DD)
file_pathNoAbsolute path/base64 Wise CSV input. Provide exactly one of file_path or file_ref.
plan_handleNoExecution-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_transfersNoSkip Jar (savings pot) transfers — internal movements within Wise (default true)
not_own_transfer_idsNoOwner-confirmed only: exact transfer Wise IDs that are payments to or from a third party, not own transfers: imported as ordinary unconfirmed rows without an ownership review. Must not overlap confirm_own_transfer_ids; a row whose own-account evidence says otherwise is held (not_own_transfer_conflicts_evidence).
counterpart_overridesNoOwner-confirmed only: { wise_id, dimension_id } picking the own bank account a transfer row goes to or from when its own-account evidence points to several (wise_transfer_counterpart_conflict). The pick must be one of the evidenced accounts, else the row stays held; an entry that decides nothing is reported (unused_counterpart_override).
accounts_dimensions_idYesBank 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_digestNoExact lowercase SHA-256 command digest returned by the reviewed dry run. Required for execute=true when mutations are planned.
fee_account_relation_idNoDeprecated alias for fee_account_dimensions_id.
confirm_own_transfer_idsNoExact Wise IDs explicitly approved as own transfers. TRANSFER-* and BANK_DETAILS_PAYMENT_RETURN-* prefixes are hints only; a hinted row whose other party is provably not an own account is imported as an ordinary unconfirmed payment (transfers_treated_as_payments).
journalized_transfer_idsNoExact { 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_idNoAccount dimension ID for the Wise fee expense account.
acknowledged_journal_holdsNoOwner-confirmed only: { wise_id, journal_ids } stating those journals do NOT book that held Wise transfer. Releases the row (imported and confirmed normally; an exact-label double-booking hold stays recorded as booked by its labelled journal) only when journal_ids lists every required_acknowledgement_ids journal of its review; never for counterpart, identity or untagged-row holds.
inter_account_dimension_idNoOther 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.

  1. Changed2 schema fields changedv0.37.0
    • changedInput schema / properties / confirm_own_transfer_ids / description
      Previous value: -"Exact Wise IDs explicitly approved as own transfers. TRANSFER-* and BANK_DETAILS_PAYMENT_RETURN-* prefixes are hints only."New value: +"Exact Wise IDs explicitly approved as own transfers. TRANSFER-* and BANK_DETAILS_PAYMENT_RETURN-* prefixes are hints only; a hinted row whose other party is provably not an own account is imported as an ordinary unconfirmed payment (transfers_treated_as_payments)."
    • addedInput schema / properties / not_own_transfer_ids
      Added value: +{
      +  "description": "Owner-confirmed only: exact transfer Wise IDs that are payments to or from a third party, not own transfers: imported as ordinary unconfirmed rows without an ownership review. Must not overlap confirm_own_transfer_ids; a row whose own-account evidence says otherwise is held (not_own_transfer_conflicts_evidence).",
      +  "items": {
      +    "minLength": 1,
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
  2. Changed2 schema fields changedv0.34.1
    • changedInput schema / properties / acknowledged_journal_holds / description
      Previous value: -"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."New value: +"Owner-confirmed only: { wise_id, journal_ids } stating those journals do NOT book that held Wise transfer. Releases the row (imported and confirmed normally; an exact-label double-booking hold stays recorded as booked by its labelled journal) only when journal_ids lists every required_acknowledgement_ids journal of its review; never for counterpart, identity or untagged-row holds."
    • addedInput schema / properties / counterpart_overrides
      Added value: +{
      +  "description": "Owner-confirmed only: { wise_id, dimension_id } picking the own bank account a transfer row goes to or from when its own-account evidence points to several (wise_transfer_counterpart_conflict). The pick must be one of the evidenced accounts, else the row stays held; an entry that decides nothing is reported (unused_counterpart_override).",
      +  "items": {
      +    "properties": {
      +      "dimension_id": {
      +        "exclusiveMinimum": 0,
      +        "maximum": 9007199254740991,
      +        "type": "integer"
      +      },
      +      "wise_id": {
      +        "minLength": 1,
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "wise_id",
      +      "dimension_id"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
  3. Changed5 schema fields changedv0.29.2
    • 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"
      +}
  4. Changed9 schema fields changedv0.25.2
    • 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"
      +]
  5. First observedv0.18.1

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare destructive=true and non-idempotent, but the description adds real domain behavior: direction-based type assignment (IN→D, OUT→C), source_direction recording, fees as separate type-C rows, and inter-account transfers avoiding double-counting against confirmed counterpart journals. It still does not describe what the dry run returns, partial-failure behavior, or re-run safety beyond the transfer note.

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?

Very compact: one lead sentence plus a single dense contract sentence, with the dry-run gate front-loaded. The second sentence is heavily packed with type codes and transfer rules, bordering on run-on, but no sentence is filler.

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 17-parameter destructive importer with no output schema, the description covers the safety gate (dry run vs execute) and the key accounting semantics (direction typing, fee rows, transfer deduplication). The main gap is that with no output schema, the shape of the dry-run report (counts, holds, review codes) is only inferable from parameter text.

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 all 17 parameters are already documented in structured fields, and the description adds little parameter-level detail beyond the execute/dry-run contract. Baseline 3 applies when the schema carries the semantics.

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?

Opens with a specific verb+resource: 'Import Wise transaction-history CSV rows.' An agent can tell this apart from the CAMT/statement importers in the sibling list by the Wise/CSV scoping. It does not explicitly name a sibling alternative, so it stops short of 5.

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 'Direct-call contract: DRY RUN by default; execute=true creates rows' clause tells the agent exactly when this mutates versus previews, and the plan_handle/digest parameters (documented in schema) reinforce the review-then-execute workflow. It gives no explicit exclusions or routing against sibling import tools, so 4 rather than 5.

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

Deploy Server

Other Tools