Skip to main content
Glama
merit-aktiva-mcp

merit-aktiva-mcp

by lauri911

Merit List Sales Offers

merit_list_sales_offers
Read-only

Lists sales quotes, orders, and prepayment invoices for a date range, including status and net/VAT totals, with filters for customer, document type, and unpaid items.

Instructions

Sales offers (pakkumised): quotes, sales orders and prepayment invoices in a period, with status (created, sent, approved, rejected, invoice created, canceled …) and amounts. TotalAmount is without VAT, TotalSum with VAT.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax rows to return (totals still cover all)
customerNoOnly customers whose name contains this
doc_typeNoWhich documentsall
date_typeNoFilter on document date, or on when it was last changeddocument
period_endYesLast day, YYYY-MM-DD (periods over 3 months are fetched in pieces; max 36 months)
unpaid_onlyNo
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

B3.4/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 safety is covered structurally. The description earns credit for disclosing that TotalAmount excludes VAT while TotalSum includes it, a real reporting gotcha, but it says nothing about ordering, pagination, truncation at the limit, or the multi-piece fetching of long periods. Useful but partial behavioral context 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?

Two sentences, front-loaded with the resource and its document kinds, with no filler. The VAT sentence is compact and informative, though it sits slightly awkwardly at the end of a definition otherwise about inputs/scope.

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

Completeness3/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 shape need not be described, and the period/doc-type/status scope is covered. However, for a 7-parameter listing tool the description omits what limit truncation means for the caller and the fact that totals span all rows, leaving the agent to rely entirely on the schema for that behavior.

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 86%, so the schema already documents nearly every parameter including limit trade-offs, customer name matching, date_type and the enum values. The description adds no per-parameter meaning beyond the schema; its only semantic contribution concerns output fields rather than inputs, which makes baseline 3 correct.

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 concrete verb+resource ('Sales offers ... in a period') and enumerates the document kinds it covers (quotes, sales orders, prepayment invoices), which lets an agent separate it from merit_list_sales_invoices and merit_get_sales_offer. It stops short of naming a sibling tool explicitly, so it is clear but not maximally differentiated.

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 usage by describing the period-scoped scope and the status/doc_type dimensions, but it gives no explicit when-to-use versus when-not-to-use guidance and never says how it differs from the invoice-listing siblings. An agent must infer that this is the pre-invoice pipeline view.

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