Skip to main content
Glama
merit-aktiva-mcp

merit-aktiva-mcp

by lauri911

Merit List Recurring Invoices

merit_list_recurring_invoices
Read-only

Lists recurring invoice contracts with customer, billing cycle, next invoice date, and per-invoice amounts so you can review upcoming automated invoices; filter by customer or date range.

Instructions

Recurring invoice contracts (perioodilised arved): customer, cycle, next invoice date, amounts per invoice. Merit makes the invoices from these on the next date.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax rows to return (totals still cover all)
customerNoOnly customers whose name contains this
date_typeNoFilter on the next invoice date, or on when the contract was last changednext_invoice
period_endNoNext invoice date until, YYYY-MM-DD; default a year after period_start
period_startNoNext invoice date from, YYYY-MM-DD; default today
include_addressesNoAlso the address each running contract's invoices go to

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 and openWorldHint, so safety is covered. The description contributes real domain context by explaining that Merit generates actual invoices from these contracts on the next invoice date, which helps interpret the data, but it says nothing about pagination behavior, freshness, or the fact that totals span all rows regardless of limit.

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 short sentences with the resource identity front-loaded and the lifecycle note second; nothing is wasted. It is terse to the point of using noun-phrase fragments, but that suits a list tool and keeps token cost low.

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 six fully documented optional parameters and an output schema, the structured fields carry most of the load, and the description supplies the conceptual meaning of the entity. Only minor gaps remain, such as the default date window's effect, which is already covered by the schema.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description edges above it by framing the entity around the next invoice date, which is exactly what the date_type/period_start/period_end filters operate on, and by mentioning customer-level data. It still adds no new syntax or constraint detail beyond the schema.

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 names the resource precisely ("Recurring invoice contracts"), lists the fields returned (customer, cycle, next invoice date, amounts per invoice), and adds an Estonian alias. It is clearly distinguishable from sibling list tools like merit_list_sales_invoices, though it never names a sibling explicitly.

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: the agent can infer this is the listing endpoint for recurring contracts, and the second sentence hints at the relationship to generated invoices. There is no explicit when-to-use guidance versus merit_get_recurring_invoice for a single contract, nor any note on when the date filters should be applied.

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