Skip to main content
Glama

Request payment

payment_collect
Idempotent

Creates the payment request for the invoice (QR bill, TWINT, card). The flow reaches PAYMENT only on the signed event of the payment provider. Needs state INVOICE. Never: Mark anything paid or pay out without a settled status. Platform fee CHF 0.10 per accepted call: quote first, then send quote_id, mandate_token and idempotency_key.

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": {
      "mandate_token": "<mandate_token>",
      "flow_id": "<flow_id>"
    },
    "name": "payment_collect"
  }
}

Input Schema

NameRequiredDescriptionDefault
methodNoHow the customer pays: qr_bill (Swiss QR bill), twint or card.
flow_idYesThe flow (job) id, which is also its chain id.
quote_idNoA valid quote for this capability (quote).
mandate_tokenYesThe mandate token from mandate.create.
idempotency_keyNoRequired on every mutate and money call; a retry with the same key returns the same result and is not charged again.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / method / description
      Added value: +"How the customer pays: qr_bill (Swiss QR bill), twint or card."
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare the write/idempotent/non-destructive profile, but the description adds material context beyond them: a CHF 0.10 platform fee per accepted call, a required quote-then-pay ordering, and the hard boundary that no payout or mark-paid may occur without a settled provider event. Return shape and failure modes are not described, which is the only notable gap.

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?

Four dense sentences, front-loaded with the action and scoping, then prerequisites, then prohibitions, then cost. The telegraphic 'Never:' fragment is slightly terse but carries no wasted text.

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 money-mutating tool with no output schema, the description covers prerequisites, sequencing with quote, idempotent retry behavior, pricing, and explicit prohibitions. An agent has everything needed to decide whether to call it and how to call it correctly.

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, but the description adds genuine semantics the schema does not: quote_id must come from a prior quote call ('quote first, then send quote_id'), and idempotency/mandate are part of a mandatory triplet. flow_id is left entirely to the schema, keeping this short of a 5.

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 verb+resource: 'Creates the payment request for the invoice', and scopes it with the payment methods (qr_bill, TWINT, card) and the resulting PAYMENT state. That distinguishes it clearly from invoice_issue or quote, though no sibling is named explicitly, so it lands just below the top of the scale.

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?

It states the prerequisite state ('Needs state INVOICE'), the mechanism ('The flow reaches PAYMENT only on the signed event of the payment provider'), and an exclusion ('Never: Mark anything paid or pay out without a settled status'). What is missing is an explicit alternative tool for the settle path, so it is clear context without routing.

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