Skip to main content
Glama

Belege auflisten

document_list
Read-only

Listet die erzeugten Dokumente des Kontos (Rechnung, Zahlungserinnerung, Mahnung, Gutschrift), neueste zuerst, gefiltert nach Art, Mandant, Empfänger oder Bezugsbeleg. Nächster Schritt: document_get liefert die vollständigen Belegdaten, document_create legt mit references einen Folgebeleg dazu an. EN: Lists the account's created documents (invoice, payment reminder, dunning letter, credit note), newest first, filtered by type, client, recipient or referenced document. Next step: document_get returns the full payload, document_create creates a follow-up document via references.

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

Input Schema

NameRequiredDescriptionDefault
limitNoStandard 20, maximal 100. EN: default 20, maximum 100.
sinceNo
offsetNoVersatz für die Seitennavigation. Standard 0. EN: offset for pagination. Default 0.
reasoningNo
documentTypeNo
recipientQueryNoFreitext über Name, Firma oder Ort des Empfängers. EN: free text over the recipient name, company or city.
mandantennummerNo
referencesNumberNo
referencesDocumentIdNoNur Dokumente, die sich auf dieses FrankKi-Dokument beziehen (z. B. alle Mahnungen zu einer Rechnung). EN: only documents referring to this FrankKi document (for example every dunning letter for one invoice).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds non-trivial context beyond them: the result is sorted newest-first and is account-scoped with the filters listed. It does not describe pagination totals or result size behavior, which keeps it from a 5.

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?

Purpose and next steps are front-loaded and every clause carries information; nothing is filler. The full German/English duplication roughly doubles the length, which is the only drag on efficiency.

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 list tool with annotations covering the safety profile and no output schema, the description supplies purpose, ordering, filter set and next-step routing. Only minor gaps remain, such as how pagination relates to the ordering or whether a total count is returned.

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 coverage is only 44%, but the description names the filter dimensions ('nach Art, Mandant, Empfänger oder Bezugsbeleg'), which map onto documentType, mandantennummer, recipientQuery and referencesNumber/DocumentId and give otherwise-undocumented params meaning. 'since' and 'reasoning' remain unexplained in both places, so it does not fully close the coverage gap.

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 and resource ('Listet die erzeugten Dokumente des Kontos') and enumerates the four document types plus the ordering ('neueste zuerst'). It explicitly separates itself from document_get (full payload) and document_create (follow-up document), so an agent can distinguish it from siblings without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The 'Nächster Schritt' sentence names both alternatives and the condition that selects them: document_get for the full record, document_create when the result should spawn a follow-up document via references. That is explicit routing rather than implied usage.

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.