Skip to main content
Glama

Get Checkout Link

get-checkout-link
Read-onlyIdempotent

The link a person opens to buy tickets or register, with Spanish instructions to relay. For paid events (card or bank transfer), checkout opens with the ticket type and quantity already chosen. For free registration, it is the event page. Nothing is reserved or charged: the person completes it themselves.

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
slugYesWhich event: its slug, from search-events or the event URL (/e/{slug}).
quantityNoFor paid events: how many tickets the person wants.
ticket_type_idNoFor paid events: the ticket type id from get-event.

Output Schema

NameRequiredDescriptionDefault
urlNoThe link to give the person. Checkout for a paid event, the event page for free registration.
modeNofree (register at no cost) or paid (buy a ticket).
totalNoPaid events: price times quantity, before fees.
methodsNoWays to pay that are open now: card, transfer. Empty for free registration.
presaleNoFree registration only: present while a followers-only presale is open.
quantityNoPaid events: tickets the checkout opens with.
ticket_typeNoPaid events: name of the chosen category.
instructionsNoHow to complete it, in Spanish. Relay it to the person.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / quantity / default
      Added value: +1
    • changedInput schema / properties / quantity / description
      Previous value: -"For paid events: how many tickets, default 1."New value: +"For paid events: how many tickets the person wants."
    • changedInput schema / properties / slug / description
      Previous value: -"The event slug."New value: +"Which event: its slug, from search-events or the event URL (/e/{slug})."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "instructions": {
      +      "description": "How to complete it, in Spanish. Relay it to the person.",
      +      "type": "string"
      +    },
      +    "methods": {
      +      "description": "Ways to pay that are open now: card, transfer. Empty for free registration.",
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "mode": {
      +      "description": "free (register at no cost) or paid (buy a ticket).",
      +      "type": "string"
      +    },
      +    "presale": {
      +      "description": "Free registration only: present while a followers-only presale is open.",
      +      "properties": {
      +        "ends_at": {
      +          "description": "When the presale ends, ISO 8601 with offset.",
      +          "type": "string"
      +        },
      +        "ticket_type_ids": {
      +          "description": "Ticket types held for followers until then.",
      +          "items": {
      +            "type": "integer"
      +          },
      +          "type": "array"
      +        }
      +      },
      +      "type": "object"
      +    },
      +    "quantity": {
      +      "description": "Paid events: tickets the checkout opens with.",
      +      "type": "integer"
      +    },
      +    "ticket_type": {
      +      "description": "Paid events: name of the chosen category.",
      +      "type": "string"
      +    },
      +    "total": {
      +      "description": "Paid events: price times quantity, before fees.",
      +      "properties": {
      +        "amount": {
      +          "description": "Decimal amount with two places, e.g. \"300.00\".",
      +          "type": "string"
      +        },
      +        "currency": {
      +          "description": "ISO currency code. Always GTQ (quetzales).",
      +          "type": "string"
      +        },
      +        "note": {
      +          "description": "What the total leaves out, in Spanish.",
      +          "type": "string"
      +        }
      +      },
      +      "type": "object"
      +    },
      +    "url": {
      +      "description": "The link to give the person. Checkout for a paid event, the event page for free registration.",
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive, so the safety profile is covered. The description adds genuinely useful context beyond that: nothing is reserved or charged, the person completes the transaction themselves, and the output includes Spanish instructions intended for relay. It does not describe link expiry or other lifecycle behavior, which would push this higher.

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?

Three short sentences, front-loaded with what the link is, then the paid/free split, then the no-charge caveat. Every sentence carries information, though the opening clause about Spanish instructions is slightly awkwardly attached and could be separated for clarity.

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 the description need not explain return values, and annotations cover the safety profile. What remains — the meaning of the link, the paid/free distinction, and the no-reservation guarantee — is present. Missing details about what the Spanish instructions contain or link expiry are minor against this coverage.

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 coverage is 100%, so the schema already documents all three parameters, including the paid-event conditionality for quantity and ticket_type_id. The description restates that paid checkout pre-selects ticket type and quantity, reinforcing but not extending the schema. Baseline 3 applies when the schema carries the parameter burden.

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 resource and its function: the URL a person opens to buy tickets or register. It also distinguishes the paid-event case (pre-filled checkout) from free registration (event page). It stops short of explicitly differentiating itself from sibling get-event, which also returns event-page information for free events.

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?

Usage is implied — call this when you need a link to hand to a buyer or registrant — but there is no explicit when-to-use or when-not-to-use statement, and no mention of when to prefer get-event instead. The paid vs free branching implicitly indicates applicability but never frames it as 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