Skip to main content
Glama

Payment link button generator

hopi_payment_link_button_generator
Read-onlyIdempotent

Make a payment link and a plain text pay button for it. type paypalme builds https://paypal.me/ with an optional amount and PayPal currency code (whole units only for HUF, JPY and TWD); revolut builds the general https://revolut.me/ link, which never carries an amount; other takes any https payment link (http and javascript: are refused). Returns the link, the button HTML for a web page and an email signature version (a table with inline styles), using your label and colours; colours below WCAG AA contrast (4.5:1) are refused. type donate returns PayPal's own Donate button SDK code instead, using hosted_button_id for a business account or business (email or payer ID) for a personal one. Nothing is checked with PayPal or Revolut. The tool page also draws a QR code for the link. Source: https://hopi.co.uk/payment-link-button-generator/

Input Schema

NameRequiredDescriptionDefault
urlNoFor type other: the full https payment link
sizeNoButton sizemedium
typeNoKind of linkpaypalme
labelNoButton text. Defaults to Pay with PayPal, Pay with Revolut or Pay now
shapeNoCorner stylerounded
amountNoOptional amount for a PayPal.Me link, up to two decimal places
newTabNoOpen the link in a new tab
revtagNoRevolut Revtag, with or without the @
currencyNoOptional PayPal currency code added after the amount
donateIdNoFor type donate: the hosted button ID (business) or the PayPal email address or payer ID (personal)
paypalMeNoPayPal.Me name: letters and numbers, up to 20 characters. A pasted paypal.me link is fine
backgroundNoButton colour as a hex code#166534
textColourNoText colour as a hex code#ffffff
accountTypeNoPayPal account for type donatebusiness

Output Schema

NameRequiredDescriptionDefault
htmlNo
linkNo
typeNo
labelNo
notesNo
summaryYes
contrastNo
warningsNo
emailHtmlNo
backgroundNo
source_urlYesThe tool's page on hopi.co.uk (cite or open to check the figure)
textColourNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Adds substantial behavior beyond the annotations: http and javascript: links are refused, colours below WCAG AA 4.5:1 are refused, HUF/JPY/TWD amounts must be whole units, revolut links never carry an amount, and nothing is verified with PayPal or Revolut. This tells the agent which inputs will bounce. It stops short of describing error responses or the exact return shape (an output schema exists anyway).

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

Conciseness3/5

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

It is a single dense paragraph with heavy semicolon and parenthesis stacking, so it reads as a run-on rather than a scannable list of modes. Every clause carries information and the core purpose is front-loaded, but the mode-by-mode breakdown would be far easier to parse as structured lines.

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?

For a 14-parameter generator with annotations and an output schema, the description covers the mode branching, validation refusals and no-server-verification caveat, which is what an agent needs to call it correctly. Minor gap: no mention of the size/shape/label/newTab styling options or how defaults are chosen, though the schema handles those.

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 already 100%, but the description still adds meaning the schema cannot: the semantic link between type and its required field (paypalMe vs revtag vs url vs donateId/accountType), the currency-code placement after the amount, and the business-vs-personal distinction for donate. That is genuine value on top of the schema baseline.

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?

Opens with a specific verb+resource: build a payment link plus a plain-text pay button, then enumerates the four distinct modes (paypalme, revolut, other, donate) and what each produces. An agent can tell exactly what it gets back without opening the schema.

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?

Each type is described with the required input and the URL shape it produces, which effectively tells the agent which type to pick for a given merchant. There is no explicit when-not-to-use guidance, though the sibling tools are unrelated calculators so cross-routing is not a real concern.

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