Skip to main content
Glama
merit-aktiva-mcp

merit-aktiva-mcp

by lauri911

Merit List Payments

merit_list_payments
Read-only

Retrieve bank and cash payments for a date range, including the invoices each payment settled, and filter by direction, counterparty, or row limit to reconcile accounts.

Instructions

Bank and cash payments in a period, with the invoices each one paid (Details).

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax rows to return (totals still cover all)
directionNoWhich paymentsall
period_endYesLast day, YYYY-MM-DD (periods over 3 months are fetched in pieces; max 36 months)
counterpartyNoOnly counterparties whose name contains this
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 and openWorldHint, so the safety profile is covered. The description adds that each payment is returned together with the invoices it paid, which is useful result context, but it says nothing about how direction affects totals, whether totals span the full period regardless of limit, or how long periods are chunked — all of which live only in the schema.

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?

A single short sentence with the resource and period scope front-loaded. The trailing '(Details)' tag is slightly cryptic, but nothing is redundant.

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 exists and the input schema is fully annotated, so the core call mechanics are covered elsewhere. What remains missing is positional context — why to choose this list over bank entries or the customer payment report — which matters given the dense set of sibling list tools.

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 all five parameters, including the direction enum and the limit/period caveats, are already documented. The description only reinforces the period scoping and contributes no additional syntax or interpretation beyond the schema, which is the expected baseline here.

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 concrete resource and scope: bank and cash payments within a period, including the invoices each payment settled. The verb is implicit ('list'), and there is no explicit differentiation from the nearby merit_list_bank_entries sibling, but the resource is specific enough that an agent can tell what it retrieves.

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?

No when-to-use or when-not-to-use guidance is given. The description never says when to prefer this over merit_list_bank_entries or merit_customer_payment_report, and it doesn't mention the direction filter as a way to narrow scope, leaving routing entirely to inference from the name.

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