Skip to main content
Glama
merit-aktiva-mcp

merit-aktiva-mcp

by lauri911

Merit Sales Report

merit_sales_report
Read-only

Generate sales reports for a period grouped by invoice, customer, or item, showing VAT-exclusive amounts and EUR values where applicable.

Instructions

Sales in a period grouped by invoice, customer or item. Amounts without VAT; C-prefixed fields are in EUR (company currency).

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": {
      "start": "<start>",
      "end": "<end>"
    },
    "name": "merit_sales_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
endYesLast day, YYYY-MM-DD (periods over 3 months are fetched in pieces; max 36 months)
limitNoMax rows to return (totals still cover all)
startYesFirst day, YYYY-MM-DD
group_byNocustomer

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations only declare readOnlyHint and openWorldHint; the description adds genuinely new behavioral context by stating amounts exclude VAT and that C-prefixed fields are in EUR (company currency). It does not repeat the schema's note about long periods being fetched in pieces or the row-limit semantics, but the currency/VAT conventions are the kind of detail an agent cannot get from annotations.

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?

Two sentences, zero waste, with the subject (sales in a period, grouped) front-loaded and the currency/VAT caveat immediately after. Every clause carries information an agent needs.

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?

An output schema exists, so return structure need not be described, and the parameters are largely self-documenting in the schema. The description covers the essential semantics (grouping, VAT exclusion, EUR prefix). Only the absence of routing guidance to related report tools 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 coverage is 75% and the schema descriptions already explain end-date splitting, the month cap, and that limits don't truncate totals. The description's contribution is clarifying what group_by means in output terms (invoices, customers, or items), which is modest added meaning over the enum plus default.

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: sales totals over a period, with the three grouping dimensions named. An agent can distinguish this aggregate report from the sibling list_sales_invoices or get_sales_invoice tools, though no sibling is named 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?

The description implies when this applies (period-based sales aggregation by invoice/customer/item), but gives no explicit when-to-use versus when-not, no mention of the profit_and_loss or invoice-listing alternatives, and no prerequisites. Usage is inferable but not guided.

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