Skip to main content
Glama

MaxRechnung

Belege auflisten

list_invoices
Read-only

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

Belege auflisten

Listet alle Belegarten: Rechnungen, Korrekturen (KR-) und Stornos (ST-). Mit type auf eine Art einschränken.

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

Input Schema

NameRequiredDescriptionDefault
typeNoBelegart filtern. Ohne Angabe: alle Arten. `invoice` ohne Abschlags- und Schlussrechnungen.
limitNoQuery-Parameter limit
numberNoExakte Belegnummer (z. B. `RE-2026-0004`) — so findet man die `id` zu einer Nummer.
offsetNoQuery-Parameter offset
statusNoQuery-Parameter status
custom_fieldsNoFilter nach eigenen Feldern: `custom_fields[schlüssel]=wert`, mehrere sind UND-verknüpft. Ja/Nein: `true` oder `false` (nicht gesetzt). Unbekannter Schlüssel → `400`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare a safe read operation (readOnlyHint=true, destructiveHint=false), so the burden is lower. The description adds one genuinely new fact — availability in every plan tier (Free, Pro, Business) — plus the KR-/ST- prefix convention, but says nothing about result paging, default page size, or what a listed record looks like.

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?

Four short lines with no padding. Minor waste: the heading 'Belege auflisten' merely repeats the title, and the plan-tier line sits ahead of the purpose statement instead of after it.

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?

With no output schema and six parameters (including a nested custom_fields object), the description should at minimum indicate what the returned records contain and how paging behaves. It covers the document-type taxonomy adequately but leaves the result shape and pagination unaddressed, and never resolves overlap with list_sales_documents.

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%, so the baseline is 3. The description only touches one of six parameters (`type`), giving hints on how to restrict to one kind of document; limit, offset, number, status and custom_fields receive no added meaning beyond 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?

The description states a specific verb and resource: 'Listet alle Belegarten: Rechnungen, Korrekturen (KR-) und Stornos (ST-)', so an agent knows this enumerates invoice-type documents rather than, say, payments. It does not distinguish the tool from the sibling list_sales_documents, which is the obvious source of confusion here.

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 only implied: the tool lists everything by default and 'Mit `type` auf eine Art einschränken' narrows it. There is no explicit statement of when to use this over list_sales_documents or how it relates to the invoice-download/creation siblings, so tool selection still requires inference.

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