Skip to main content
Glama
Sign In
BankConv MCP server

BankConv MCP server

by wassim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get the transactions of a conversion

get_transactions
Read-only

Retrieve transactions from an earlier BankConv conversion by conversion ID to inspect dated, signed amounts and running balances with bank, account, period and currency details.

Instructions

Get the transactions of an earlier BankConv conversion by its conversion id (from convert_statement or list_conversions): ISO date, description, signed amount (money in positive) and running balance, with the bank, account, period and currency. Read-only; uses no pages. To save a file instead, use download_statement. Errors say what went wrong: not_found for an unknown conversion id, gone once a conversion was deleted under data retention (24 hours by default), unreadable_statement when the tables can't be read as transactions (the message names the row), insufficient_credits when the account has too few pages.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "conversion_id": "<conversion_id>"
    },
    "name": "get_transactions"
  }
}

Input Schema

NameRequiredDescriptionDefault
tablesNoAdvanced: which tables to read, as page:table indexes from 0 ("0:1,1:0"). Leave out and BankConv picks the transaction tables.
conversion_idYesThe conversion id, as returned by convert_statement or list_conversions.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.1
    • changedInput schema / properties / conversion_id / description
      Previous value: -"The conversion id."New value: +"The conversion id, as returned by convert_statement or list_conversions."
  2. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already flag readOnlyHint and openWorldHint, but the description adds real value beyond them: no page consumption, the 24-hour retention window that makes a conversion 'gone', and four named error codes including insufficient_credits. This is strong disclosure; only minor gap is no note on result size or ordering guarantees.

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?

Purpose is front-loaded in the first clause, followed by return shape, the alternative, and errors. The error enumeration runs long in a single sentence, but every item is actionable, so little is wasted.

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?

With no output schema, the description must describe the return payload, and it does: date, description, signed amount, running balance, plus bank, account, period and currency. Combined with error codes and retention behavior, an agent has enough to call and interpret results; only edge cases like empty conversions or pagination are unaddressed (and pagination is stated as not applicable).

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 both parameters are already documented, and the description only repeats the conversion_id provenance. It adds nothing about the advanced 'tables' parameter's page:table syntax or when to override the default.

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 (get the transactions of a conversion) plus the identifier used to locate it, and names the sibling tools that produce that id (convert_statement or list_conversions). An agent can distinguish this from list_conversions and download_statement without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicitly says where conversion_id comes from and names the alternative for a different goal: 'To save a file instead, use download_statement.' That is a clear positive routing instruction with no ambiguity.

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