Skip to main content
Glama

FrankKi

by app.frankki
OverviewDiscussionsAdmin

Beleg erstellen

document_create

Erzeugt aus strukturierten Belegdaten ein fertiges Dokument und legt es als Briefentwurf an: FrankKi rechnet Positionen, Netto, USt-Sätze und Brutto nach, prüft die Pflichtangaben nach § 14 UStG, vergibt auf Wunsch die Belegnummer aus deinem Nummernkreis und setzt alles im DIN-5008-Layout mit deinem Briefdesign. Der Entwurf bleibt kostenfrei liegen, bis du ihn versendest. Alle Beträge in ganzen Cent. Kompaktes Beispiel: {"document":{"documentType":"rechnung","documentNumber":"RE-2026-014","documentDate":"2026-07-30","leistungszeitraum":{"von":"2026-06-01","bis":"2026-06-30"},"zahlungszielTage":14,"lineItems":[{"description":"Beratung Juni","quantity":4,"unit":"Std","unitPriceCents":12000,"ustRate":19,"lineNetCents":48000}],"totals":{"nettoCents":48000,"ustLines":[{"rate":19,"netCents":48000,"ustCents":9120}],"bruttoCents":57120}},"recipientAddressId":"…"} Nächster Schritt mit der zurückgegebenen letterId: order_send versendet den Brief, approval_submit legt ihn stattdessen einem Menschen zur Freigabe vor, letter_schedule versendet ihn später. EN: Turns a structured billing payload into a finished document and stores it as a letter draft: FrankKi re-computes line items, net, VAT rates and gross, checks the mandatory details under § 14 UStG, optionally draws the document number from your sequence, and typesets everything in the DIN 5008 layout with your letter design. The draft stays free of charge until you send it. All amounts in integer cents. Compact example: {"document":{"documentType":"rechnung","documentNumber":"RE-2026-014","documentDate":"2026-07-30","leistungszeitraum":{"von":"2026-06-01","bis":"2026-06-30"},"zahlungszielTage":14,"lineItems":[{"description":"Beratung Juni","quantity":4,"unit":"Std","unitPriceCents":12000,"ustRate":19,"lineNetCents":48000}],"totals":{"nettoCents":48000,"ustLines":[{"rate":19,"netCents":48000,"ustCents":9120}],"bruttoCents":57120}},"recipientAddressId":"…"} Next step with the returned letterId: order_send sends the letter, approval_submit puts it in front of a human for approval instead, letter_schedule sends it later.

Input Schema

NameRequiredDescriptionDefault
subjectNoBetreff des Briefs. Ohne Angabe setzt FrankKi ihn aus Dokumentart und Belegnummer, z. B. 'Rechnung RE-2026-014'. EN: letter subject. If omitted FrankKi builds it from the document type and number.
designIdNo
documentYesDie Belegdaten. Alle Beträge in ganzen Cent. Du lieferst die Summen, FrankKi rechnet sie nach und lehnt Abweichungen ab. EN: the document payload. All amounts in integer cents. You supply the sums, FrankKi re-computes them and rejects mismatches.
languageNoStandard de. EN: defaults to de.
reasoningNo
referenceNo
signatureIdNo
sequenceScopeNo
clientLetterIdNoIdempotenzschlüssel für den Briefentwurf. EN: idempotency key for the letter draft.
mandantennummerNoMandant, dem das Dokument zugeordnet wird. Nur Zuordnung für Liste und Auswertung. EN: client this document is filed under. Filing only.
senderAddressIdNo
senderProfileIdNoAbsenderprofil, aus dem die Pflichtangaben (USt-IdNr oder Steuernummer) gelesen werden. Ohne Angabe gilt dein Standardprofil. EN: sender profile the mandatory tax details are read from. Defaults to your default profile.
includeSignatureNo
recipientAddressIdNoEmpfänger aus deinem Adressbuch (address_list / mandant_search liefern die id). Entweder das oder recipientAddressInline. EN: recipient from your address book. Either this or recipientAddressInline.
recipientAddressInlineNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changed
    • changedInput schema / properties / clientLetterId / description
      Previous value: -"Idempotenzschluessel fuer den Briefentwurf. EN: idempotency key for the letter draft."New value: +"Idempotenzschlüssel für den Briefentwurf. EN: idempotency key for the letter draft."
    • changedInput schema / properties / document / description
      Previous value: -"Die Belegdaten. Alle Betraege in ganzen Cent. Du lieferst die Summen, FrankKi rechnet sie nach und lehnt Abweichungen ab. EN: the document payload. All amounts in integer cents. You supply the sums, FrankKi re-computes them and rejects mismatches."New value: +"Die Belegdaten. Alle Beträge in ganzen Cent. Du lieferst die Summen, FrankKi rechnet sie nach und lehnt Abweichungen ab. EN: the document payload. All amounts in integer cents. You supply the sums, FrankKi re-computes them and rejects mismatches."
    • changedInput schema / properties / document / properties / kleinunternehmerParagraph19 / description
      Previous value: -"§19 UStG Kleinunternehmer: keine USt-Zeile, Brutto gleich Netto, Pflichthinweis wird ergaenzt. EN: German small-business rule: no VAT line, gross equals net, the mandatory note is added."New value: +"§19 UStG Kleinunternehmer: keine USt-Zeile, Brutto gleich Netto, Pflichthinweis wird ergänzt. EN: German small-business rule: no VAT line, gross equals net, the mandatory note is added."
    • changedInput schema / properties / document / properties / lineItems / items / properties / quantity / description
      Previous value: -"Menge, hoechstens 3 Nachkommastellen. EN: quantity, at most 3 decimals."New value: +"Menge, höchstens 3 Nachkommastellen. EN: quantity, at most 3 decimals."
    • changedInput schema / properties / document / properties / numberFromSequence / description
      Previous value: -"true = FrankKi zieht die naechste Nummer aus deinem Nummernkreis. Dann documentNumber weglassen. EN: true = FrankKi draws the next number from your sequence; omit documentNumber then."New value: +"true = FrankKi zieht die nächste Nummer aus deinem Nummernkreis. Dann documentNumber weglassen. EN: true = FrankKi draws the next number from your sequence; omit documentNumber then."
    • changedInput schema / properties / document / properties / references / description
      Previous value: -"Bezug auf ein frueheres Dokument. documentId fuer ein Dokument aus FrankKi, documentNumber fuer einen Fremdbeleg. EN: reference to a prior document."New value: +"Bezug auf ein früheres Dokument. documentId für ein Dokument aus FrankKi, documentNumber für einen Fremdbeleg. EN: reference to a prior document."
    • changedInput schema / properties / document / properties / references / properties / zahlungszielDatum / description
      Previous value: -"Zahlungsziel des Bezugsbelegs, also seit wann die Forderung offen ist. Wird auf Mahnung und Zahlungserinnerung als \"Zahlungsziel ueberschritten seit\" gedruckt. EN: due date of the referenced document, printed on a dunning letter or reminder as the date since when the claim is overdue."New value: +"Zahlungsziel des Bezugsbelegs, also seit wann die Forderung offen ist. Wird auf Mahnung und Zahlungserinnerung als \"Zahlungsziel überschritten seit\" gedruckt. EN: due date of the referenced document, printed on a dunning letter or reminder as the date since when the claim is overdue."
    • changedInput schema / properties / document / properties / totals / properties / extraLines / description
      Previous value: -"Freie Zeilen unter dem Bruttobetrag. Geprueft wird nur die Rechnung, die die Zeile selbst behauptet. EN: free-form lines below the gross total, checked only for the arithmetic the line itself claims."New value: +"Freie Zeilen unter dem Bruttobetrag. Geprüft wird nur die Rechnung, die die Zeile selbst behauptet. EN: free-form lines below the gross total, checked only for the arithmetic the line itself claims."
    • changedInput schema / properties / mandantennummer / description
      Previous value: -"Mandant, dem das Dokument zugeordnet wird. Nur Zuordnung fuer Liste und Auswertung. EN: client this document is filed under. Filing only."New value: +"Mandant, dem das Dokument zugeordnet wird. Nur Zuordnung für Liste und Auswertung. EN: client this document is filed under. Filing only."
    • changedInput schema / properties / recipientAddressId / description
      Previous value: -"Empfaenger aus deinem Adressbuch (address_list / mandant_search liefern die id). Entweder das oder recipientAddressInline. EN: recipient from your address book. Either this or recipientAddressInline."New value: +"Empfänger aus deinem Adressbuch (address_list / mandant_search liefern die id). Entweder das oder recipientAddressInline. EN: recipient from your address book. Either this or recipientAddressInline."
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare write/non-destructive/closed-world. The description adds real behavior beyond them: FrankKi re-computes and rejects mismatching sums, the draft carries no cost until sent, the layout is DIN 5008 with the user's letter design, and mandatory § 14 UStG details are validated. It still says nothing about permissions or quota/rate limits on document creation.

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 sentence is front-loaded and efficient, but the entire description is duplicated in German and English, including the identical JSON example twice, which roughly doubles length without adding information. The bilingual duplication costs more than the marginal accessibility benefit at this length.

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?

With no output schema, the description compensates by naming the returned letterId and the three tools that consume it, and by explaining the document payload semantics and the recompute-and-reject rule. Given 15 parameters and deep nesting, more could be said about the unillustrated top-level fields, but an agent has enough to call it correctly in the common case.

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 coverage is 47%, below the bar where the schema alone suffices. The embedded worked example meaningfully illustrates the nested 'document' payload (documentType, documentNumber, leistungszeitraum, zahlungszielTage, lineItems, totals) plus recipientAddressId, but roughly half the top-level parameters (designId, signatureId, senderProfileId, reference, sequenceScope, clientLetterId, mandantennummer, language) get no mention at all.

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?

The description names a specific verb and resource ('Erzeugt aus strukturierten Belegdaten ein fertiges Dokument und legt es als Briefentwurf an') and enumerates the distinctive pipeline: recompute line items/net/VAT/gross, § 14 UStG mandatory-detail check, optional number draw, DIN 5008 typesetting with the letter design. That makes it separable from the plain-letter sibling letter_create_draft without opening either schema.

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?

It gives clear downstream routing — order_send sends, approval_submit routes to a human, letter_schedule defers — and notes the draft is free until sent, which is useful context. But it never states when to choose this tool over letter_create_draft or what prerequisites (e.g. sender profile, address book entry) must exist first. Usage is implied rather than explicit.

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

All FrankKi toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources