Skip to main content
Glama

MaxRechnung

Belege auflisten

list_sales_documents
Read-only

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

Belege auflisten

Angebote, Auftragsbestätigungen und Lieferscheine, neueste zuerst. Filter nach Belegart, Status, Nummer und Kette. Angebote sind ab Pro, Auftragsbestätigungen und Lieferscheine ab Business: unter Pro antwortet jeder /sales-documents-Endpunkt mit 403 plan_required; in Pro ebenso, wer eine Auftragsbestätigung oder einen Lieferschein anlegt, deren Status setzt oder dorthin weiterführt (details nennt type bzw. target).

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

Input Schema

NameRequiredDescriptionDefault
typeNoQuery-Parameter type
limitNoQuery-Parameter limit
numberNoExakte Belegnummer, z. B. AN-2026-0004.
offsetNoQuery-Parameter offset
statusNoQuery-Parameter status
chain_idNoAlle Belege einer Kette (Wurzel-id).
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

A3.6/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 adds genuine behavior beyond that: newest-first ordering, plan-based 403 plan_required failures, and that error details name `type`/`target`. It does not cover pagination semantics or the shape of the result list.

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 title 'Belege auflisten' is repeated verbatim as a line of the description, and the opening 'Tarif: in jedem Tarif (Free, Pro, Business)' is immediately qualified by plan restrictions on quotes and order confirmations, which reads as self-contradictory on first pass. The plan paragraph is dense but informative; the redundancy and the buried structure cost points.

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 7-parameter, no-output-schema list tool, the description covers ordering, all filter axes at a high level, and failure behavior (403 plan_required with detail fields). The remaining gap is pagination/result-size expectations for limit/offset, which is minor given the fully documented schema.

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 enum values for type/status and the custom_fields syntax are already documented in the schema. The description only restates the filter axes (Belegart, Status, Nummer, Kette) and adds the plan gating per type, without mentioning limit, offset, or custom_fields. 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 states a concrete verb and resource ('Belege auflisten') and enumerates the resource types (Angebote, Auftragsbestätigungen, Lieferscheine) plus ordering ('neueste zuerst'), so an agent knows this is a filtered list operation, distinct from get/create/update siblings. It does not explicitly name a sibling alternative, which keeps it short of a 5.

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?

It gives an explicit when-not condition: under Pro, every /sales-documents endpoint answers 403 plan_required, and order confirmations/delivery notes require Business. That is real availability guidance an agent can act on. It stops short of a 5 because it never routes to an alternative tool (e.g. get_sales_document or a filtered list elsewhere).

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