Skip to main content
Glama

Rechnungslotse: deutsche E-Rechnung

Pflichtangaben nach § 14 UStG prüfen

pflichtangaben_pruefen
Read-only

Prüft die Angaben einer Rechnung gegen § 14 UStG – auch für eine Rechnung aus Word oder einem PDF ohne Datensatz. Meldet je Pflichtangabe, ob sie vorhanden ist, und berücksichtigt Kleinbetragsrechnungen (§ 33 UStDV), Kleinunternehmer (§ 19) und Reverse Charge (§ 13b).

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

Input Schema

NameRequiredDescriptionDefault
ibanNo
nettoNoNettobetrag in Euro, z. B. 1190.00
leistungNoBezeichnung der Leistung oder Ware.
ausstellerNoWer die Rechnung stellt.
empfaengerNo
ust_prozentNo19, 7 oder 0, in der Land- und Forstwirtschaft nach § 24 UStG 7.8 oder 5.5.
leistungsdatumNoJJJJ-MM-TT – Liefer- oder Leistungszeitpunkt.
rechnungsdatumNoJJJJ-MM-TT
reverse_chargeNoSteuerschuldnerschaft des Leistungsempfängers?
rechnungsnummerNo
kleinunternehmerNoGilt § 19 UStG?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / ust_prozent / description
      Previous value: -"19, 7 oder 0."New value: +"19, 7 oder 0, in der Land- und Forstwirtschaft nach § 24 UStG 7.8 oder 5.5."
  2. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true, so the description carries the substantive burden and does add value: it states the result granularity ('Meldet je Pflichtangabe, ob sie vorhanden ist') and that Kleinbetragsrechnungen (§ 33 UStDV), Kleinunternehmer (§ 19) and Reverse Charge (§ 13b) are accounted for. It does not say whether the check aborts, warns, or how missing fields are represented, but the legal-variant handling is real added context.

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?

Two dense sentences, front-loaded with purpose then result behaviour and legal exceptions; every clause carries information. The statutory citations are efficient shorthand rather than padding, though the second sentence is long.

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?

For an 11-parameter, nested, no-output-schema validation tool the description explains the result shape and legal variants, which covers the main gaps. However, it claims to handle a Word or PDF invoice 'ohne Datensatz' while the schema exposes no file or attachment parameter, leaving the agent unsure how such an invoice is supplied.

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?

With 73% schema coverage over 11 parameters including nested issuer/recipient objects, the schema does most of the work. The description references Kleinunternehmer and Reverse Charge, which map to the kleinunternehmer and reverse_charge flags, but adds no format, requiredness, or interaction semantics (e.g. what happens when fields are omitted).

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?

Names a specific verb and object ('Prüft die Angaben einer Rechnung gegen § 14 UStG') and adds a distinct scope: per-mandatory-field presence reporting, including invoices from Word or PDF without a stored record. It does not name the near-identical siblings (pflicht_pruefen, rechnung_pruefen), so differentiation is left partly to inference.

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?

The description implies when it applies (checking an invoice's § 14 UStG mandatory details, including paper/PDF invoices without a dataset), which is a useful usage cue. It gives no explicit when-not guidance and never routes the agent away from the similar-sounding pflicht_pruefen or rechnung_pruefen siblings.

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