Skip to main content
Glama

MaxRechnung

Summen je Kunde, Status oder Monat

get_invoice_summary
Read-only

Tarif: in jedem Tarif (Free, Pro, Business).

Summen je Kunde, Status oder Monat

Serverseitig gerechnete Summen über die Belege (Rechnungen, Korrekturen, Stornos): Anzahl, netto, USt., brutto, bezahlt, offen und überfällig je Gruppe und gesamt. Gruppen nach Netto absteigend (Monate chronologisch) — so beantwortet man „Welcher Kunde brachte am meisten Umsatz?“ ohne selbst zu addieren. Stornierte Belege zählen nie, Entwürfe nur mit include_drafts=true; beide stehen gezählt in excluded. Korrekturen (KR-) mindern mit negativen Beträgen die Summe ihres Kunden.

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": "get_invoice_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoRechnungsdatum bis (einschließlich), `YYYY-MM-DD`.
fromNoRechnungsdatum ab (einschließlich), `YYYY-MM-DD`.
typeNoBelegart filtern. Ohne Angabe: alle Arten.
statusNoNur Belege mit diesem Status. `draft` schließt Entwürfe automatisch ein.
group_byNo`customer` (Kunden-id, sonst Empfängername), `status` oder `month` (Rechnungsmonat `YYYY-MM`).customer
include_draftsNoEntwürfe mitzählen (Standard: nein — Entwürfe sind kein Umsatz).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description still adds real behavioral context beyond them: cancelled documents never count, drafts require include_drafts=true and are reported in `excluded`, and corrections reduce sums with negative amounts. Sort order (net descending, months chronological) is also disclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core paragraph is information-dense and useful, but the first two lines waste space: the title is restated verbatim in the description body and the tier line is phrased redundantly ("in jedem Tarif (Free, Pro, Business)"). Front-loading is spent on repetition rather than the key behavior.

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?

There is no output schema, so the description must carry return-value semantics, and it does: it enumerates the aggregate fields, explains grouping and sort order, and accounts for `excluded`. Only the exact shape of the per-group versus total structure is left implicit.

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, and most parameters are already well documented in the schema. The description adds meaning on the interaction between include_drafts, drafts, and the `excluded` output, plus how correction documents affect grouped totals — genuinely beyond the schema text.

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 (server-side computed sums) over a specific resource (Belege: Rechnungen, Korrekturen, Stornos) with explicit grouping options (Kunde, Status, Monat) and enumerates the aggregates returned (Anzahl, netto, USt., brutto, bezahlt, offen, überfällig). This clearly separates it from per-document siblings like get_invoice or get_sales_document.

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 a concrete when-to-use reason — answering "Welcher Kunde brachte am meisten Umsatz?" without manual addition — and notes it is available in every tier. It does not name an alternative tool or state when not to use it, so it stops short of explicit routing.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources