Skip to main content
Glama
iseppo

e-arveldaja MCP Server

by iseppo

Import Wise Transactions

import_wise_transactions
Destructive

Import transaction history from Wise CSV exports into e-arveldaja bank accounts, supporting dry runs, date range filters, and automatic fee/inter-account transfer handling.

Instructions

Import Wise transaction-history CSV rows. Direct-call contract: DRY RUN by default; execute=true creates rows; preserve import direction as type D incoming / type C outgoing; fees use separate 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)
date_fromNoOnly import transactions from this date (YYYY-MM-DD)
file_pathYesAbsolute path to the regular Wise transaction-history.csv export from Transactions.
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
fee_account_relation_idNoDeprecated alias for fee_account_dimensions_id.
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?

Beyond the annotations (destructiveHint, not idempotent), the description adds rich behavioral details: dry-run by default, direction mapping, fees as separate transactions, and inter-account transfer double-counting avoidance. This fully informs the agent of expected behavior.

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

Conciseness5/5

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

The description is remarkably concise, with no superfluous words. It front-loads the core action and presents key details in a structured yet natural flow, each sentence earning its place.

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 tool with 9 parameters and no output schema, the description covers the essential behavioral aspects: dry-run, execution, direction, fees, inter-account transfers. It lacks explicit mention of CSV format prerequisites but implies it. Overall, it is sufficiently complete for an agent to use correctly.

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 100% with descriptions for each parameter. The description adds overarching context (e.g., direction preservation, fee handling) that indirectly aids understanding of parameters, though it does not elaborate on individual parameter semantics beyond 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 the tool imports Wise transaction-history CSV rows, with specific verb and resource. It details the dry-run default, execution flag, direction preservation, fee handling, and inter-account transfer logic, distinguishing it from other import tools among siblings.

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 description provides clear context for use, including default dry-run behavior and when execution occurs. However, it does not explicitly mention when not to use this tool or suggest alternative tools among the listed siblings.

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