Skip to main content
Glama
merit-aktiva-mcp

merit-aktiva-mcp

by lauri911

Merit Customer Debts

merit_customer_debts
Read-only

Retrieve outstanding customer debts document by document, including due dates and unpaid amounts; filter by customer, as-of date, and overdue days.

Instructions

What customers owe (receivables), document by document, with due dates and unpaid amounts.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "merit_customer_debts"
  }
}

Input Schema

NameRequiredDescriptionDefault
as_ofNoDebt on this date, YYYY-MM-DD; default today
limitNoMax rows to return (totals still cover all)
customerNoPart of a customer's name; empty = all customers
overdue_daysNoOnly documents overdue by more than this many days

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/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. The description adds that results are per-document with due dates and unpaid amounts, which tells the agent what kind of rows come back, but it says nothing about totals rows, truncation behavior at the limit, or whether fully paid documents appear.

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?

A single front-loaded sentence that defines the resource, the granularity (document by document), and the key fields, with no filler or redundancy.

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, return values need not be explained, and the annotations cover read-only safety; the description plus schema together are enough to call the tool correctly. It is slightly thin on what a 'document' encompasses (invoices, credit notes) for a receivables report, which keeps it from a 5.

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%, and the schema already explains as_of, limit (including that totals cover all rows), customer name matching, and overdue_days. The description adds no parameter-level 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?

The description gives a concrete verb-and-resource picture: it returns receivables, broken out document by document, including due dates and unpaid amounts. That is clearly distinguishable from report siblings in substance, but it never names an alternative such as merit_customer_payment_report, so sibling differentiation is left to inference.

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: an agent can infer this is the tool for 'who owes us money and how overdue', but there is no explicit when-to-use statement, no mention of when to prefer the payment report or the sales invoice list, and no prerequisites.

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