McpStamp QR Codes and Barcodes

SEPA payment QR code

qr_payment_sepa

Call this tool for an EPC069-12 payment QR a euro banking app can scan. Amount and reference are enough: the beneficiary IBAN and name default to the shared business profile, never asked for.

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

Input Schema

Name	Required	Description
`bic`	No	Beneficiary BIC. Optional under EPC version 002
`iban`	No	Beneficiary IBAN. Defaults to the iban in the shared business profile (set once with the invoice server's business_set). Checked with ISO 7064 mod 97 and refused if it does not validate
`name`	No	Beneficiary name, up to 70 characters. Defaults to the name in the shared business profile
`size`	No	PNG width in pixels, 32 to 4000 (default 300). SVG scales without it
`amount`	No	Amount in EUR, 0.01 to 999999999.99. Leave out and the payer types it
`format`	No	svg (default, free) or png (Pro)
`margin`	No	Quiet zone in modules, default 4, which is what the QR standard requires
`purpose`	No	Four-letter ISO 20022 purpose code, for example GDDS
`currency`	No	EUR only; any other value is refused, because EPC encodes a SEPA credit transfer
`out_path`	No	Name for the downloaded file, e.g. acme-code. SVG is returned inline when this is left out; a PNG always comes back as a download link valid for one hour
`overwrite`	No	Replace a file of the same name already produced in this request (default false)
`reference`	No	Structured creditor reference (RF...), up to 35. Use this OR remittance, never both
`remittance`	No	Free payment text, up to 140 characters, for example an invoice number
`error_correction`	No	L 7%, M 15% (default), Q 25%, H 30% of the code recoverable when damaged

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 6, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- removedInput schema / properties / size / maximum
```
Removed value: -9007199254740991
```
- removedInput schema / properties / size / minimum
```
Removed value: --9007199254740991
```
Changed3 schema fields changedNov 6, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
- addedInput schema / properties / size / maximum
```
Added value: +9007199254740991
```
- addedInput schema / properties / size / minimum
```
Added value: +-9007199254740991
```
First observedOct 14, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations only cover mutability/idempotence/destruction flags, so the description carries the burden of behavioral context. It adds a useful fact: beneficiary IBAN and name default to the shared business profile and are never asked for. It does not discuss output behavior, file creation, authentication needs, or side effects, though those are partially hinted at in the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences with no filler. The usage condition is front-loaded, and the default-beneficiary behavior is stated in the second sentence. Every phrase earns its place.

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 a 14-parameter tool with no output schema, the description plus schema is mostly sufficient, and the shared-profile context is valuable. However, the description does not describe the return contract (inline SVG versus downloadable PNG) and does not clarify how this tool relates to invoice_payment_qr; the agent must infer these from the out_path parameter and sibling names.

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 earns extra credit by emphasizing the minimal viable payload ('Amount and reference are enough') and clarifying that beneficiary data is supplied by defaults rather than required input. This helps an agent assemble a valid call without opening every schema field.

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?

The description opens with a specific action ('Call this tool for an EPC069-12 payment QR') and names a concrete output (a QR a euro banking app can scan). It is clearly distinguished from barcode, wifi, and vcard QR tools, though it never explicitly names or separates itself from the close sibling invoice_payment_qr.

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 description gives an explicit trigger condition: use this for an EPC069-12 SEPA payment QR. It also gives practical guidance that amount and reference are enough, and that beneficiary IBAN/name come from the shared profile. It does not name alternatives or state when not to use it, so it stops short of a 5.

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

All McpStamp QR Codes and Barcodes tools Inspect

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.