Skip to main content
Glama

GrowVib: Social Media Growth

create_checkout

Create a checkout session: a payment link a PERSON opens and pays in their own USDC wallet (Base or Solana), for when you cannot sign a payment yourself or the user wants to pay with their own wallet. Pick the service with search_catalog or recommend_service and price it with get_quote first, then call this with service_id, quantity and link. The result carries page_url (give it to the person), the exact amount, expires_at (the price is held until then, 30 minutes by default) and a token for get_checkout_status. Creating a session moves no money and reserves nothing: nothing is charged until the person signs in their wallet, and an unpaid session simply expires. Each call opens a NEW session, so call it once per intended order and reuse the token you were given. Prefer create_paid_order when you hold a wallet and should pay yourself.

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": {
      "quantity": "<quantity>",
      "link": "<link>"
    },
    "name": "create_checkout"
  }
}

Input Schema

NameRequiredDescriptionDefault
linkYesThe target link the order is delivered to.
quantityYesQuantity to order.
return_urlNoOptional https URL shown to the person as a link after paying (where they came from). Never followed by the server.
service_idNoThe service: its id or its slug (e.g. telegram-members) from search_catalog or get_service. May be omitted when service_option_id is given, since an option names its service.
ttl_secondsNoOptional: hold the price for LESS than the default 30 minutes. A larger value is clamped to the default, never granted.
external_refNoOptional reference of your own (an order or conversation id, at most 128 characters), echoed by get_checkout_status.
service_option_idNoThe plan option: the full id from options[].id in get_service or search_catalog. Optional: without it the service's Express card is priced (its recommended setup, else its cheapest card that takes the quantity), else the cheapest plain option that fits, and the quote names it. Alone, it also names the service.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / service_option_id / description
      Previous value: -"The plan option: the full id from options[].id in get_service or search_catalog. Optional: without it the service's primary option is priced. Alone, it also names the service."New value: +"The plan option: the full id from options[].id in get_service or search_catalog. Optional: without it the service's Express card is priced (its recommended setup, else its cheapest card that takes the quantity), else the cheapest plain option that fits, and the quote names it. Alone, it also names the service."
  2. Changed3 schema fields changed
    • changedInput schema / properties / service_id / description
      Previous value: -"The service id from search_catalog."New value: +"The service: its id or its slug (e.g. telegram-members) from search_catalog or get_service. May be omitted when service_option_id is given, since an option names its service."
    • changedInput schema / properties / service_option_id / description
      Previous value: -"Optional specific service option id; defaults to the service's primary option."New value: +"The plan option: the full id from options[].id in get_service or search_catalog. Optional: without it the service's primary option is priced. Alone, it also names the service."
    • changedInput schema / required
      Previous value: -[
      -  "service_id",
      -  "quantity",
      -  "link"
      -]New value: +[
      +  "quantity",
      +  "link"
      +]
  3. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare non-readonly, non-idempotent, non-destructive, open-world, but the description adds the substance an agent needs: no money moves, nothing is reserved, nothing is charged until the person signs, unpaid sessions simply expire. It also discloses the 30-minute default hold, that expires_at bounds the price, and that each call opens a NEW session with a reusable token.

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 core definition and sibling routing, then workflow, then return values. It is dense but long, with slight redundancy in "moves no money and reserves nothing: nothing is charged until the person signs" and "an unpaid session simply expires" covering overlapping ground.

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?

No output schema exists, yet the description enumerates the return fields (page_url, exact amount, expires_at, token) and instructs what to do with each. Combined with the workflow prerequisites and the no-charge semantics, an agent has everything needed to call it correctly.

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%, so the schema already documents every parameter including ttl_seconds clamping and the service_option_id fallback. The description only names service_id, quantity and link as the call arguments and adds no new syntax or constraint detail, so it sits at the baseline.

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 ("Create a checkout session") and immediately defines it as "a payment link a PERSON opens and pays in their own USDC wallet (Base or Solana)". This makes it unambiguously distinct from create_paid_order, which the description names as the alternative.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit selection criteria: use when you cannot sign a payment yourself or the user wants to pay with their own wallet, and prefer create_paid_order when you hold a wallet. It also sequences prerequisites (search_catalog or recommend_service, then get_quote, then this call) and warns to call once per intended order.

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