Skip to main content
Glama

Get checkout link

get_checkout_link
Read-onlyIdempotent

Use this when the traveller picks a plan. Returns a haalaan.com link; the traveller pays there. Nothing is charged here.

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": {
      "slug": "<slug>"
    },
    "name": "get_checkout_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesPlan slug from search_esims (lowercase letters, digits and hyphens).

Output Schema

NameRequiredDescriptionDefault
urlYes
planYes
policyYes
expiresYes
supportYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / slug / description
      Added value: +"Plan slug from search_esims (lowercase letters, digits and hyphens)."
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, but the description adds something structurally absent: that the actual payment happens off-platform and no charge occurs in this call. That is exactly the kind of context an agent needs to avoid narrating a charge or retrying a paid action. It stops short of mentioning link validity/expiry or reuse, which matters for handing a link to a user.

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, the trigger condition first, the returned artifact second, the safety caveat last. No filler and no restatement of the tool name or title.

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?

An output schema exists, so return-value shape needs no explanation, and the one required parameter is fully documented in the schema. For a single-parameter link-generation tool the description is nearly sufficient; the one gap an agent would care about is link lifetime or what to do if the traveller doesn't complete payment.

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% and the slug property already documents its format and its origin in search_esims, so the description adds nothing about the parameter. With one fully documented parameter, 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 description states a concrete outcome — it returns a haalaan.com link where the traveller pays — and the domain plus 'the traveller pays there' make it distinguishable from search_esims and list_destinations. It never uses the words 'checkout link' or 'create', so the verb is implied rather than stated, which keeps it just short of a 5.

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?

'Use this when the traveller picks a plan' gives an explicit trigger condition, and 'Nothing is charged here' implicitly excludes it from being a payment/booking tool. It does not name the sibling that supplies the input (search_esims) in the description, though the schema does, and no explicit when-not guidance is given.

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