Skip to main content
Glama
iseppo

e-arveldaja MCP Server

by iseppo

Import Wise Transactions

import_wise_transactions
Destructive

Import Wise transaction-history CSV rows into e-arveldaja with dry run support. Handles fees, transfer directions, and inter-account transfers to prevent double-counting.

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
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)
accounts_dimensions_idYesBank account dimension ID for the Wise account in e-arveldaja
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.
fee_account_dimensions_idNoAccount dimension ID for the Wise fee expense account.
inter_account_dimension_idNoOther bank account dimension ID for inter-account transfers. Auto-detected if only one other bank account exists; required with 3+ bank accounts.
Behavior5/5

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

Discloses key behaviors beyond annotations: dry run default, fee transactions as separate, inter-account transfer handling. Annotations indicate destructiveHint=true, but description adds crucial context.

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?

Single paragraph with dense but relevant information. Could be broken into sentences for readability, but no wasted words.

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?

Covers all critical aspects: dry run, execution, fee handling, transfer handling, and provides enough context for a complex tool with 13 parameters and no output schema.

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 coverage is 100%, so baseline 3. The description does not add detail beyond schema for individual parameters, but the overall behavioral context complements the schema.

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 it imports Wise transaction-history CSV rows and details the dry-run/execute behavior. It is distinct from sibling tools, which focus on individual transactions or invoices.

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?

Provides guidance on dry-run vs. execute, fee separation, and inter-account transfers. Does not explicitly mention alternatives or when not to use, but the context implies it is the sole tool for importing Wise CSV data.

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/iseppo/e-arveldaja-mcp'

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