Skip to main content
Glama
Sign In
e-arveldaja MCP Server

e-arveldaja MCP Server

by iseppo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Process CAMT.053

process_camt053
Destructive

Parse CAMT.053 bank statements, preview transaction imports with a dry run, and create approved transactions in e-arveldaja. Use it to verify entries before posting.

Instructions

Merged CAMT.053 entry point. Use mode='parse' to inspect a bank statement, mode='dry_run' to preview transaction import, or mode='execute' to create transactions after approval.

Input Schema

NameRequiredDescriptionDefault
modeNoWorkflow phase to run. Defaults to parse.
detailNoOutput detail on standard/full. Default compact: no sample rows, duplicates listed briefly, every held row kept. full = the complete envelope. Presentation only; not part of the reviewed plan.
date_toNoOnly import entries up to this date (YYYY-MM-DD)
file_refNoOpaque Accounting Inbox CAMT file reference. Provide exactly one of file_path or file_ref.
date_fromNoOnly import entries from this date (YYYY-MM-DD)
file_pathNoAbsolute path/base64 input. Provide exactly one of file_path or file_ref.
plan_handleNoExecution-plan handle returned by the reviewed dry run. Required for mode='execute'.
accounts_dimensions_idNoBank account dimension ID in e-arveldaja. Required for dry_run and execute modes.
skip_inter_account_legsNoOwn-account transfers (counterparty IBAN = another own bank account): leave out this side's outgoing or incoming legs because the other account's statement books them. Default none. Bound into the plan.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.39.0
    • addedInput schema / properties / detail
      Added value: +{
+  "description": "Output detail on standard/full. Default compact: no sample rows, duplicates listed briefly, every held row kept. full = the complete envelope. Presentation only; not part of the reviewed plan.",
+  "enum": [
+    "compact",
+    "full"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / skip_inter_account_legs
      Added value: +{
+  "description": "Own-account transfers (counterparty IBAN = another own bank account): leave out this side's outgoing or incoming legs because the other account's statement books them. Default none. Bound into the plan.",
+  "enum": [
+    "none",
+    "outgoing",
+    "incoming"
+  ],
+  "type": "string"
+}
  2. Changed1 schema field changedv0.29.2
    • addedInput schema / additionalProperties
      Added value: +false
  3. Changed4 schema fields changedv0.25.2
    • changedInput schema / properties / file_path / description
      Previous value: -"Absolute path to the CAMT.053 XML file."New value: +"Absolute path/base64 input. Provide exactly one of file_path or file_ref."
    • addedInput schema / properties / file_ref
      Added value: +{
+  "description": "Opaque Accounting Inbox CAMT file reference. Provide exactly one of file_path or file_ref.",
+  "type": "string"
+}
    • addedInput schema / properties / plan_handle
      Added value: +{
+  "description": "Execution-plan handle returned by the reviewed dry run. Required for mode='execute'.",
+  "type": "string"
+}
    • removedInput schema / required
      Removed value: -[
-  "file_path"
-]
  4. First observedv0.18.1

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, openWorldHint=true and non-idempotent, so the risk profile is structured data. The description adds meaningful context beyond that by showing only the execute phase writes and that it must follow an approved dry run, but it says nothing about reversibility of created transactions, rate limits, or authentication requirements.

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?

A single front-loaded sentence that names the entry point and then enumerates the three phases in workflow order, with no filler or repetition.

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 9-parameter, potentially destructive tool with no output schema, the description covers the crucial phase gating but leaves gaps: it does not describe what parse returns, how the plan handle is carried between dry_run and execute, or how duplicate handling relates to cleanup_camt_possible_duplicate. Still workable because the schema documents all parameters and annotations carry the risk profile.

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 every parameter including mode, detail, plan_handle and skip_inter_account_legs is already documented in the schema; the baseline of 3 applies. The description restates the mode semantics without adding format, default, or constraint detail beyond what the enum descriptions provide.

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?

States a specific verb and resource (process a CAMT.053 bank statement) and immediately decomposes it into three named workflow phases, so an agent knows this is the merged single entry point. It does not distinguish itself from nearby siblings such as parse_lightyear_statement or accounting_inbox, which would be needed for 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 Guidelines4/5

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

Gives explicit mode-selection guidance: parse to inspect, dry_run to preview the import, execute to create transactions after approval. That is clear when-to-use context for the tool's own phases, but it never says when to reach for this tool rather than a sibling like accounting_inbox or cleanup_camt_possible_duplicate.

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