Skip to main content
Glama
Sign In

payqr

by dev.cz-agents
OverviewDiscussionsAdmin

qr_payment_batch

Read-only

PAID. Create payment QR codes for a whole batch of payments in one call — e.g. an invoice run. The free qr_payment tool handles one payment per call; this one returns the whole set. Requires payment via x402; call without payment first to receive the terms.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "payments": "<payments>"
    },
    "name": "qr_payment_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
paymentsYesUp to 50 payments. Each QR is generated and verified independently.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior1/5

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

The description claims 'Create payment QR codes', a write operation, but annotations set readOnlyHint=true. This is a direct contradiction. While the description does add behavioral context (payment requirement), the contradiction undermines trust.

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?

Three concise sentences, front-loaded with 'PAID'. Every sentence adds value: batch purpose, differentiation from sibling, and payment workflow. No wasted words.

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?

Given no output schema, the description explains it returns the whole set. It mentions independent verification per QR. Lacks detail on exact return format, but adequate for basic use with sibling tool context.

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?

Input schema covers 100% of parameters with descriptions; the 'payments' array and its sub-properties are fully documented. The description adds batch context but no additional parameter semantics beyond what the schema provides.

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 clearly states the tool creates payment QR codes for a batch, specifies the use case ('invoice run'), and distinguishes itself from the sibling 'qr_payment' tool which handles one payment per call.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly tells when to use this tool (for batch) vs 'qr_payment' (single). Also mentions payment requirement via x402 and instructs to call without payment first to receive terms.

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

All payqr 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