Skip to main content
Glama
merit-aktiva-mcp

merit-aktiva-mcp

by lauri911

Merit Purchase Report

merit_purchase_report
Read-only

Generates purchase reports for a date range, grouping spend by invoice, vendor, or item and returning VAT-exclusive amounts for bookkeeping analysis.

Instructions

Purchases in a period grouped by invoice, vendor 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_purchase_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_byNovendor

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/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 the safety profile is covered. The description adds genuinely useful domain behavior that annotations cannot: amounts exclude VAT and C-prefixed fields are in EUR company currency, which prevents misinterpretation of returned figures. It does not restate the chunking/36-month limits, but those live in the schema.

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 compact sentences with zero filler, front-loading the core purpose before the currency/VAT caveat. Every clause carries information an agent would otherwise have to guess.

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-value explanation is unnecessary, and the description covers the tricky interpretive details (VAT exclusion, EUR-prefixed fields). The remaining gap is routing guidance relative to the many sibling report tools, which would help an agent pick 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 coverage is 75%, and the one undocumented parameter is group_by, whose enum values are spelled out in the description ('grouped by invoice, vendor or item'). That is real added meaning beyond the schema, though start/end semantics are left entirely to 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?

States a specific verb+resource: purchases over a period, grouped by invoice/vendor/item. This clearly separates it from a sales or P&L report, though it never names a sibling tool explicitly. An agent knows what the tool produces without opening the schema.

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 implied by 'Purchases in a period grouped by...', which signals a period-based aggregate report, but there is no explicit when-to-use versus merit_sales_report, merit_profit_and_loss, or the invoice-listing tools. No prerequisites or exclusions are stated.

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