Skip to main content
Glama
merit-aktiva-mcp

merit-aktiva-mcp

by lauri911

Merit List Bank Entries

merit_list_bank_entries
Read-only

Lists payments booked to a bank account or imported bank statement rows for a period, with optional document lines and totals.

Instructions

One bank account's payments booked in Merit (income or expense), or the bank statement rows imported into it. Amounts in each row's own currency.

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": {
      "bank": "<bank>",
      "period_start": "<period_start>",
      "period_end": "<period_end>"
    },
    "name": "merit_list_bank_entries"
  }
}

Input Schema

NameRequiredDescriptionDefault
bankYesBankId, or part of the bank account's name or IBAN (merit_reference_list kind=banks)
kindNoincome / expense: payments in or out of this account booked in Merit, with the documents each settled; statement_imports: bank statement rows imported into Meritincome
limitNoMax rows to return (totals still cover all)
date_typeNoincome / expense: filter on document date or on when it was entered; statement_imports always use the booking datedocument
period_endYesLast day, YYYY-MM-DD (periods over 3 months are fetched in pieces; max 36 months)
with_linesNostatement_imports: also the lines of each imported row
period_startYesFirst day, YYYY-MM-DD

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered and the bar is lower. The description adds a genuinely useful behavioral fact — amounts are reported in each row's own currency, so no conversion or summation across currencies should be assumed — but says nothing about row/limit behavior or the totals that the schema's limit field alludes to.

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?

Two tight sentences with the scope front-loaded and the currency caveat trailing appropriately. Nothing is redundant, though the sentence is dense enough that the two modes (payments vs statement imports) could be split for scannability.

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?

An output schema and full annotation coverage exist, so return-shape explanation is not required. However, for a seven-parameter tool spanning two data modes, the description omits any guidance on mode selection trade-offs and on the period-size constraint, leaving the schema to carry all operational context.

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%, with enums for kind and date_type and defaults documented inline, so the baseline of 3 applies. The description contributes only the currency note and the income/expense vs statement-imports framing, which the schema already spells out in more detail.

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?

The description states a concrete resource and scope: payments booked in Merit for one bank account, or the statement rows imported into it, with the currency convention noted. An agent can distinguish this from a general payments listing by the per-bank-account scoping, though no sibling is named explicitly, so the differentiation is implicit rather than stated.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance: nothing says how this differs from merit_list_payments or why one would choose it over the general payment list, and no prerequisite (such as resolving a bank id first) is stated in the description. The mode distinctions live in the schema's kind enum, not in the description's guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.