Skip to main content
Glama
Sign In
Payware MCP Server

Payware MCP Server

Official
by payware
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

payware_poi_get_qrcode

Read-onlyIdempotent

Generate a QR code image for a POI so customers can scan it for printing or screen display. Supports PNG, SVG, and JPG output using the required POI ID.

Instructions

[Merchant] Generate a QR code image for a POI that customers can scan.

Endpoint: GET /poi/{poiId}/image Authentication: your own JWT Use Case: Generate QR codes for printing or displaying on screens.

Formats: PNG (default), SVG, JPG

Returns the image itself (MCP image content); an SVG comes back as its markup.

Required: POI ID.

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": {
      "poiId": "<poiId>"
    },
    "name": "payware_poi_get_qrcode"
  }
}

Input Schema

NameRequiredDescriptionDefault
poiIdYesThe POI identifier (format: pi + 8 alphanumeric chars, e.g., piABC12345)
formatNoImage format (default: PNG)PNG
useSandboxNoUse sandbox environment for testing

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.2.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, so the safety profile is covered; the description adds relevant behavior not in the annotations — the HTTP endpoint, that authentication uses the caller's own JWT, and crucially the return shape (binary image content, with SVG returned as markup). It omits whether output is cached or how sandbox behaves, but adds real value beyond the structured fields.

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 one-line purpose, then scannable labeled sections for endpoint, auth, use case, formats, and return. The formatting is slightly heavy for a single-parameter tool, but no line is superfluous.

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?

With no output schema, the description correctly compensates by explaining what comes back (image content, SVG as markup) — the most important missing structured information for an agent handling the response. Remaining gaps are minor: no note on image dimensions or the default sandbox=true behavior.

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?

Schema description coverage is 100%, so all three parameters (including the sandbox flag and POI ID format) are already documented. The description restates the format options and required POI ID rather than adding new meaning, so the baseline of 3 applies.

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 opening line gives a specific verb and resource ('Generate a QR code image for a POI that customers can scan') plus a '[Merchant]' audience tag, which no sibling tool overlaps with. It stops short of explicitly naming a contrasting sibling, but the purpose is unambiguous.

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?

'Use Case: Generate QR codes for printing or displaying on screens' gives a usage context but no when-not conditions and no alternative tool for cases where a POI ID is unknown or where an existing image should be retrieved. Usage selection is only implied.

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

Deploy Server

Other Tools