Skip to main content
Glama
merit-aktiva-mcp

merit-aktiva-mcp

by lauri911

Merit Get Sales Invoice

merit_get_sales_invoice
Read-only

Retrieve a single sales invoice with header, line items, accounts, VAT, and payments received. Use the invoice ID or number to fetch full billing details, with optional PDF or delivery note text.

Instructions

One sales invoice in full: header, lines (items, accounts, VAT), payments received.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "merit_get_sales_invoice"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoSIHId from merit_list_sales_invoices
invoice_noNoInvoice number, if the id is not known
include_pdfNoAlso return the invoice PDF's text as Merit prints it
delivery_noteNoWith include_pdf: the delivery note (the invoice without prices) instead

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations only say readOnly and openWorld; the description adds the substantive fact that the response is a fully expanded invoice with header, lines (items, accounts, VAT) and payments. That return-shape disclosure matters because there is no output schema. It stays short of 5 by not noting behavior when neither identifier is provided.

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?

A single front-loaded sentence with a colon that lists the payload contents; every clause conveys something an agent needs, and there is no filler.

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?

For a read-only four-parameter retrieval tool with no output schema, the description adequately conveys the returned structure and the schema covers the inputs. The remaining gap is the absence of any statement about needing id or invoice_no, or about PDF/delivery-note interaction beyond the schema's own notes.

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%, with each parameter documented in-schema (id, invoice_no fallback, include_pdf, delivery_note). The description adds no additional meaning about these parameters, so the baseline 3 applies.

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?

The description names a specific resource (one sales invoice) and enumerates what it returns: header, lines with items/accounts/VAT, and payments received. This distinguishes it from the sibling list tool merit_list_sales_invoices, which returns many. The verb itself is implicit ('One sales invoice in full'), so it stops short of a clean 5.

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?

No guidance on when to fetch a single invoice instead of using merit_list_sales_invoices, and no mention of the requirement that one of id or invoice_no be supplied. The only routing hint lives in the schema ('SIHId from merit_list_sales_invoices'), not in the description.

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