Skip to main content
Glama
merit-aktiva-mcp

merit-aktiva-mcp

by lauri911

Merit List Gl Batches

merit_list_gl_batches
Read-only

List general ledger entries for a date period, one row per entry, with optional batch-type filtering and debit/credit line details.

Instructions

General ledger entries (pearaamatu kanded) in a period, one row per entry.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax rows to return (totals still cover all)
batch_codeNoOnly this batch type, e.g. MA sales invoices, OA purchase invoices, PA payments
period_endYesLast day, YYYY-MM-DD (periods over 3 months are fetched in pieces; max 36 months)
with_linesNoAlso each entry's debit and credit lines per account (period max 12 months)
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

C2.8/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 without description help. The description adds only that results are period-scoped with one row per entry; it says nothing about the paging/piecewise-fetch behavior, the 3- and 36-month period ceilings, or the with_lines expansion that the schema hints at. Useful but thin beyond the annotations.

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 front-loaded clause with a parenthetical translation and a granularity note; nothing is padded or redundant. It is efficient, though the brevity borders on under-specification rather than tightness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has five parameters, date-range paging rules, a batch-type filter, and an optional line-level expansion, plus a sibling that fetches a single GL batch. The description addresses none of this and leaves the batch-vs-entry naming unresolved, so an agent must reconstruct the tool's role from the name and schema alone.

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%, documenting limit, batch_code, with_lines, and both date bounds with their format and period caps, so the schema carries the parameter burden. The description contributes no additional parameter meaning (no default reversal, no batch_code examples, no interaction between with_lines and the 12-month cap). Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a resource ('General ledger entries / pearaamatu kanded') and a scope ('in a period'), plus a granularity hint ('one row per entry'), so the general purpose is inferable. However, it never reconciles 'batches' in the tool name with 'entries' in the description, and it does not distinguish this from merit_get_gl_batch or the other merit_list_* tools. That ambiguity keeps it at vague-but-usable rather than clearly differentiated.

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 at all, and no named alternative. An agent gets no signal for choosing this over merit_get_gl_batch, merit_list_bank_entries, or merit_list_payments.

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