No user-submitted related servers found.
Scored across 10 tools
Most tools are clearly separated by payload type (qr_create for text/URL, qr_wifi, qr_vcard, barcode_create, barcode_batch, code_list, and the two license tools). However, invoice_payment_qr and qr_payment_sepa both produce a SEPA payment QR from an amount and reference using the shared business profile's IBAN, so an agent can easily pick the wrong one. The descriptions hint at a difference (invoice_id lookup vs. raw amount), but the boundary is thin and the names do not reinforce it.
The set follows a readable <domain>_<action> convention: qr_*, barcode_*, code_list, license_*. The only real deviations are invoice_payment_qr, which inverts the order used by its near-twin qr_payment_sepa, and the noun_noun license_status alongside noun_verb license_activate. These are minor and still parseable.
Ten tools is a well-scoped set for a QR/barcode generator, with each family (QR types, barcode, batch, history, licensing) earning its place. The only questionable inclusions are two license tools and two near-duplicate payment tools, which nudge it just over the minimum needed.
The core lifecycle is covered: generate single codes (text, WiFi, vCard, SEPA), generate barcodes and batches, list history, and manage licensing. Gaps are minor rather than blocking: no structured QR types beyond WiFi/vCard/payment (e.g. email, SMS, geo), no decode/read-back of an existing code, and no way to delete or prune generated files or history entries.