Skip to main content
Glama

get_payment_link

Destructive

Create or refresh a secure payment link for an existing booking.

This call creates externally observable payment-provider and booking state,
then returns payment_url, the operator's own payment page covering every
reserved leg of the trip, together with included_bookings and the total.
Where the payment card is displayed, it shows the legs and total, opens
payment_url and marks the trip paid once payment settles; without the card,
payment_url is the traveller's only way to pay. Sóley never processes
payments directly — the operator is the merchant of record.

If the consolidated link would span bookings started in different sessions
on the same phone, the response is 'requires_confirmation' instead of a URL:
relay the included bookings + total to the traveller, then re-call with
confirm=true once approved.

The response transaction_mode is demo, sandbox, or live. If demo_notice is
present, relay it exactly; live responses intentionally omit demo_notice and
use the normal payment copy.

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": {
      "booking_reference": "<booking_reference>",
      "operator_id": "<operator_id>"
    },
    "name": "get_payment_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoLeave false on the first call. If the response comes back with 'requires_confirmation': true, the link would combine bookings from more than one shopping session on this phone — show the traveller the 'included_bookings' and total, and only after they confirm those all belong to this trip, call get_payment_link again with confirm=true. If some are not wanted, cancel_booking them first.
operator_idYesUnique operator slug, e.g. 'fosshotel-reykjavik' or 'arctic-adventures'. Obtain from search_operators. Do not guess — always look up first.
booking_referenceYesBooking reference code returned by create_booking.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses that the call creates externally observable payment-provider and booking state, that the operator is merchant of record and Sóley never processes payments, that a requires_confirmation response replaces the URL, and that transaction_mode varies across demo/sandbox/live with demo_notice needing exact relay. The non-readOnly, non-idempotent, openWorld annotation profile is consistent with this and enriched by it.

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 action in the first sentence, then layered: return values, the confirmation branch, then transaction modes. It is longer than typical but nearly every sentence carries an operational fact; the payment-card display explanation is the one passage an agent could infer quickly.

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 three-parameter mutation tool with an output schema, the description covers outcomes, the branching error path, and the demo/live copy distinction. Nothing an agent needs to call it correctly or handle its response is missing.

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 meaning the schema alone does not: the semantic condition that triggers requires_confirmation (bookings started in different sessions on the same phone) and what to do with included_bookings. The confirm parameter itself is already fully documented in the schema, so this is reinforcement rather than new parameter data.

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?

Names a specific verb and resource ("Create or refresh a secure payment link for an existing booking") and scopes it to existing bookings, which distinguishes it from create_booking and get_price_quote in the sibling list. An agent can tell immediately what it produces: a payment_url.

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?

Establishes the precondition (an existing booking), points to search_operators for operator_id and create_booking for booking_reference, and prescribes the two-step confirm flow when the link would span sessions. It does not explicitly state when not to use this instead of get_price_quote or create_booking, so it stops just short of full routing guidance.

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