Skip to main content
Glama

Bhutan Trips by Druk Asia

Create Payment Link

create_payment

Creates an Airwallex payment link for a booking and returns a URL the traveller opens to pay securely. Never ask the user for card numbers or CVCs in chat — card details are only ever entered on the payment page. Requires a valid Druk Asia API key (sent automatically via the x-api-key header).

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": {
      "online_booking_id": "<online_booking_id>",
      "booking_ref_code": "<booking_ref_code>",
      "amount": "<amount>"
    },
    "name": "create_payment"
  }
}

Input Schema

NameRequiredDescriptionDefault
amountYesPayment amount in USD.
booking_ref_codeYesBooking reference code, e.g. DA-26-X7K2PQ.
online_booking_idYesOnlineBookings.Id (booking_id from create_booking).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / booking_ref_code / minLength
      Removed value: -1
    • addedInput schema / properties / booking_ref_code / pattern
      Added value: +"^[A-Za-z0-9_-]{1,64}$"
    • removedInput schema / properties / card_number
      Removed value: -{
      -  "description": "Card number (required for auto_fill).",
      -  "type": "string"
      -}
    • removedInput schema / properties / cvc
      Removed value: -{
      -  "description": "Card CVC (required for auto_fill).",
      -  "type": "string"
      -}
    • removedInput schema / properties / expiry_month
      Removed value: -{
      -  "description": "Card expiry month (required for auto_fill).",
      -  "type": "string"
      -}
    • removedInput schema / properties / expiry_year
      Removed value: -{
      -  "description": "Card expiry year (required for auto_fill).",
      -  "type": "string"
      -}
    • removedInput schema / properties / name
      Removed value: -{
      -  "description": "Cardholder name (required for auto_fill).",
      -  "type": "string"
      -}
    • removedInput schema / properties / online_booking_id / minLength
      Removed value: -1
    • addedInput schema / properties / online_booking_id / pattern
      Added value: +"^[A-Za-z0-9_-]{1,64}$"
    • removedInput schema / properties / payment_type
      Removed value: -{
      -  "description": "auto_fill charges a card directly; payment_link generates a payment URL.",
      -  "enum": [
      -    "auto_fill",
      -    "payment_link"
      -  ],
      -  "type": "string"
      -}
    • changedInput schema / required
      Previous value: -[
      -  "online_booking_id",
      -  "booking_ref_code",
      -  "amount",
      -  "payment_type"
      -]New value: +[
      +  "online_booking_id",
      +  "booking_ref_code",
      +  "amount"
      +]
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations declare the safety profile (not read-only, open-world, non-idempotent, non-destructive), so the bar is lower; the description still adds genuine value by naming the external provider, disclosing that a URL is returned, and flagging the auth mechanism (Druk Asia API key via x-api-key, sent automatically). It does not warn that a repeat call creates a second link/payment charge, which is the main risk implied by idempotentHint=false.

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 short sentences, front-loaded with what it does and what it returns, followed by the safety constraint and auth note. Every sentence carries distinct information with no repetition of the schema.

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, describing the return as a URL is the right compensation, and the auth requirement is covered. What is missing is link lifetime/expiry and the consequence of duplicate invocation, both of which matter for a non-idempotent payment-creating tool.

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% with only three required parameters, all documented in-schema including the USD unit and booking_ref_code example. The description adds no further semantics about amount currency handling, rounding, or how booking_ref_code relates to online_booking_id, so baseline 3 applies.

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?

States a specific verb and resource ("Creates an Airwallex payment link for a booking") and its outcome ("returns a URL the traveller opens to pay securely"), which cleanly separates it from the read-only sibling get_payment_status.

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?

The payment-flow context is clear (create the link, hand it to the traveller), and it gives a firm exclusion about never collecting card details in chat. However, it never names an alternative for retrieving payment state (e.g. get_payment_status) or states preconditions such as when a booking is eligible for a link.

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