Skip to main content
Glama
merit-aktiva-mcp

merit-aktiva-mcp

by lauri911

Merit List Purchase Invoices

merit_list_purchase_invoices
Read-only

Retrieve purchase invoices for a date range, including vendor, amounts, and payment status. Filter to unpaid invoices to see what the company still owes vendors.

Instructions

Purchase invoices (ostuarved) in a period: bill number, dates, vendor, amounts, paid or not. Use unpaid_only for what the company still owes vendors. TotalAmount is without VAT, TotalSum with VAT. Invoices waiting for approval are not in the books yet: approve, correct or delete them in Merit (merit_get_purchase_invoice cannot open them).

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax rows to return (totals still cover all)
statusNobooked: invoices in the books; waiting_approval: entered but not yet approved in Meritbooked
vendorNoOnly vendors whose name contains this
date_typeNoFilter on document date, or on when it was last changed (for waiting_approval: when it was entered)document
period_endYesLast day, YYYY-MM-DD (periods over 3 months are fetched in pieces; max 36 months)
unpaid_onlyNoOnly unpaid ones (booked invoices only)
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

A4.5/5.0
Behavior4/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 genuine domain context beyond that: TotalAmount excludes VAT while TotalSum includes it, and invoices awaiting approval are not yet in the books, which explains a non-obvious data-visibility boundary. Pagination/row-cap behavior is left to the schema rather than the prose.

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?

Three short, front-loaded statements: what is listed, how the amount fields differ, and the approval-state caveat. No filler sentences and no repetition of the schema.

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

Completeness5/5

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

With an output schema present, a fully documented 7-parameter schema, and annotations covering the safety profile, the description supplies exactly the missing layer: the notion of VAT in the two total fields and the boundary around unapproved invoices. An agent has everything needed to select and call it correctly.

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 description coverage is 100%, so the baseline is 3; the description earns above that by giving business meaning to filters — unpaid_only as 'what the company still owes vendors' and the waiting_approval status as 'not in the books yet'. It does not elaborate on date_type or the limit interaction, which the schema already documents.

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

Purpose5/5

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

States a specific verb and resource ('Purchase invoices (ostuarved) in a period') and immediately enumerates the fields returned: bill number, dates, vendor, amounts, paid status. It also distinguishes itself from the sibling read tool by noting merit_get_purchase_invoice cannot open waiting-approval invoices.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Gives concrete when-to-use guidance: 'Use unpaid_only for what the company still owes vendors' and explains that pending invoices must be handled in Merit. It does not give explicit exclusion guidance (e.g. when to prefer merit_purchase_report or merit_list_payments over this list), so it stops short of the top band.

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