Skip to main content
Glama

Invoice Generator API - JSON to PDF invoice with SEPA pay QR

invoice_generator
Read-onlyIdempotent

Send seller, buyer and line items as JSON, get a clean A4 PDF invoice (base64): number, dates, quantities, prices, VAT %, subtotal/VAT/total, bank details and, for EUR + IBAN, a SEPA QR code that banking apps scan to pay. Unicode (Cyrillic, Greek, accents). No watermark, nothing stored. Runs on our server, < 0.5 s. Free: 25 calls/day per IP. Paid: $0.005 per call via x402 at https://radarbg.com/x402/invoice-generator.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "vat": "19",
      "iban": "DE89370400440532013000",
      "buyer": "Client GmbH\nHafen 2, Hamburg",
      "items": [
        {
          "price": 400,
          "quantity": 1,
          "description": "Web design"
        },
        {
          "price": 5,
          "quantity": 12,
          "description": "Hosting (months)"
        }
      ],
      "number": "2026-001",
      "seller": "Example Ltd\nMain St 1, Berlin"
    },
    "name": "invoice_generator"
  }
}

Input Schema

NameRequiredDescriptionDefault
bicNoYour BIC
dueNoDue date YYYY-MM-DD
vatNoVAT percent, e.g. 20
dateNoYYYY-MM-DD (default today)
ibanNoYour IBAN (adds bank details + SEPA pay QR)
buyerNoCustomer name and address
itemsYesLines: [{description, quantity, price}]
notesNoFooter notes, e.g. payment terms
titleNoHeading, default INVOICE
numberNoInvoice number
sellerNoYour name and address (new lines allowed)
currencyNo3-letter currency, default EUR

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, openWorld), and the description layers on genuinely useful behavior: nothing is stored, no watermark, server-side execution under 0.5 s, Unicode handling, per-IP daily quota, and the paid x402 path. Rate limits and statelessness are exactly the kind of context annotations cannot express.

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?

Front-loaded with the core transform, then supporting facts, with no filler sentences. It is dense and list-like in places (price/latency/limits packed into one paragraph), which costs a little readability but nothing is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 12-parameter, single-required-field generator with no output schema, the description covers the return type (base64 PDF), the derived fields, conditional QR behavior, cost, quota, and latency. An agent has everything needed to decide to call it and to interpret the result.

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 100%, so the baseline is 3; the description adds conditional meaning the schema omits — the SEPA QR only appears when currency is EUR and an IBAN is supplied, and subtotal/VAT/total are derived rather than passed in. It doesn't elaborate on formatting expectations for dates or addresses, but the added conditional logic is real value.

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 concrete transform: 'Send seller, buyer and line items as JSON, get a clean A4 PDF invoice (base64)', and enumerates the produced artifacts (number, dates, VAT breakdown, totals, bank details, SEPA QR). This is clearly distinguishable from siblings like sepa_xml or e_invoice_reader, which produce XML or parse invoices rather than render a PDF.

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?

The usage context is clear — you supply invoice data as JSON and receive a rendered PDF, with the SEPA QR appearing only for EUR + IBAN. It also gives operational guidance (free 25 calls/day per IP, paid $0.005/call via x402), though it never names an alternative tool or a when-not-to-use condition.

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