Skip to main content
Glama
todesstoss

monobank-mcp

by todesstoss
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

monobank-personal-statement

Read-onlyIdempotent

Fetch Monobank account transactions for a date range up to 31 days. Get details like amounts, balances, fees, cashback, and merchant info to track spending and reconcile accounts.

Instructions

Returns a list of transactions for a Monobank account. Maximum range is 31 days per request.

Inputs:

  • accountId: account id from monobank-personal-client-info. Use '0' for the default UAH account.

  • fromDate: start of range, ISO 8601 with timezone (e.g. '2026-06-01T00:00:00+03:00').

  • toDate: end of range, ISO 8601 with timezone. Defaults to now if omitted.

Each transaction:

  • amount: transaction amount in base currency unit. Negative = debit (money out), positive = credit (money in).

  • operationAmount: original amount in the operation currency (differs from amount when currencyCode != account currency).

  • currencyCode: ISO 4217 code of the operation currency.

  • balance: account balance after this transaction.

  • commissionRate / cashbackAmount: fee charged and cashback earned, in base currency unit.

  • mcc / originalMcc: Merchant Category Code (ISO 18245).

  • hold: true if the transaction is pending (not yet settled).

  • description: merchant or transfer name.

  • receiptId / invoiceId: identifiers for receipt lookup.

  • counterName / counterIban / counterEdrpou: counterparty info for transfers (present when available).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toDateNo
fromDateYes
accountIdYes

Tool Definition Quality

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnly/openWorld/idempotent/non-destructive, and the description adds substantive behavior: date range limit, timestamp defaulting, sign conventions, pending holds, and counterparty fields. This greatly exceeds annotation-only transparency.

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?

Starts with a one-sentence summary, then groups inputs and output fields clearly. Every section earns its place, with no redundancy. The structured layout makes the length acceptable given the tool's complexity.

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?

With no output schema, the description carries the full burden of explaining the return value, and it does so comprehensively: amount semantics, currency, balance, fees, MCC, hold status, and counterparty data. Input constraints and defaults are also covered, making the tool fully usable.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Input schema has 0% description coverage, but the description fully compensates: it explains accountId source and default '0', gives ISO 8601 format examples for fromDate/toDate, and documents toDate defaulting. All parameters are meaningfully described.

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?

Description opens with 'Returns a list of transactions for a Monobank account' — a specific verb and resource. This clearly distinguishes it from sibling tools like monobank-bank-currency and webhook management tools.

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 clear context: maximum 31-day range, accountId sourced from 'monobank-personal-client-info', and toDate defaults to now. It doesn't explicitly name alternatives, but the domain is so distinct that usage context is sufficient.

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/todesstoss/monobank-mcp'

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