Skip to main content
Glama
merit-aktiva-mcp

merit-aktiva-mcp

by lauri911

Merit Customer Payment Report

merit_customer_payment_report
Read-only

Generates a customer payment report for a date range, showing each document’s total, unpaid amount, due date, and overdue days to track receivables.

Instructions

Merit's customer payment report: customers' documents in a period with total, unpaid amount, due date and how overdue each is.

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_customer_payment_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax rows to return (totals still cover all)
currencyNoOnly documents in this currency, e.g. EUR
customerNoPart of a customer's name; empty = all customers
period_endYesLast day, YYYY-MM-DD
customer_idNoExact CustomerId (merit_find_customers)
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

A3.5/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 the safety profile is covered. The description usefully discloses the report's contents (totals, unpaid amounts, due dates, overdue aging), but says nothing about the cursor/limit interaction or that totals span all rows regardless of limit — that critical caveat is 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?

One front-loaded sentence that names the report and then lists its outputs; no filler. It is slightly packed (the 'how overdue each is' clause is a bit loose) but every clause carries information.

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 an output schema present and full schema coverage, the description only needed to establish what the report is and what it returns, which it does. The remaining gap is comparative guidance against merit_customer_debts and the other report siblings.

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%, including the important 'totals still cover all' note on limit and the overlap caveat on customer vs customer_id. The description adds no parameter meaning beyond that, so the baseline of 3 applies.

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+resource ('customer payment report') and enumerates the fields returned (total, unpaid amount, due date, overdue age), which lets an agent tell it apart from the invoice-listing siblings. It does not explicitly distinguish itself from merit_customer_debts, which sounds adjacent, so it stops short of 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 Guidelines3/5

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

Usage is only implied by the required period_start/period_end fields — the agent can infer 'use this to review a period's receivables'. There is no explicit when-to-use, when-not-to-use, or named alternative, and the only routing hint (merit_find_customers for customer_id) lives in the schema rather than the description.

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