Skip to main content
Glama

Start a purchase the person completes themselves

create_checkout

Return a payment link for the person to open in a browser: either a subscription plan, or a single image bought outright (only where price.card_available is true) — or that image's commercial license, with licence=commercial, where price.commercial is not null. The commercial license is sold only this way; Stripe's page asks the person to name the licensee. THE AGENT NEVER HANDLES CARD DETAILS and must not ask for any — hand the url over and let the person pay on the payment page. Nothing is granted until they finish. After a one-off, call fulfil_image with the same listing_id: once the payment has landed it delivers the image at no credit cost, and until then it answers payment_pending. After a subscription, get_account shows it. Every result lists the plans with their prices. Use fulfil_image instead when the buyer already has credits or already owns the image, and start_trial when they have none and have not tried the store. Refused when the buyer already owns the image or already has a subscription, so that nobody pays twice — except an image the free trial bought, which is the screen file only: a one-off for it buys the print file at the full price. Each new link cancels the previous one — any earlier subscription link, or an earlier link for the same image — so give the person only the latest.

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

Input Schema

NameRequiredDescriptionDefault
kindYes
licenceNoFor kind=one_off. "commercial" buys the business licence, by card only; omit for personal.
plan_codeNoFor kind=subscription. Call with kind=subscription and no plan_code to list the plans and their prices.
listing_idNoFor kind=one_off: the image to buy outright.

Output Schema

NameRequiredDescriptionDefault
kindYes
plansYes
order_idYes
expires_atYes
listing_idYes
checkout_urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false, destructiveHint=false, openWorldHint=true, but the description adds substantial context beyond them: the agent must never handle card details, nothing is granted until payment completes, and each new link cancels prior links. Minor gap: it doesn't say whether the call needs auth or what the refusal response looks like, but the safety-relevant behavior is well disclosed.

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?

Purpose is front-loaded, and the dense single paragraph carries follow-up actions, refusals, and link-cancellation semantics that each earn their place. It is long but not padded; a slightly more segmented structure would help scanning.

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?

Given a mutation with an output schema present (so return format needn't be described), the description covers the full lifecycle: what to do after one-off (fulfil_image), after subscription (get_account), and how refusals and link cancellation work. Nothing an agent needs to call it correctly 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 75% and the description adds real meaning beyond it — commercial licence only where price.commercial is not null, one-off only where price.card_available is true, and omitting plan_code lists plans. The listing_id usage is thin, but the enum semantics are enriched.

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 action — returning a payment link — and names the exact purchase variants (subscription plan, one-off image, commercial licence) with their preconditions. An agent can tell this apart from fulfil_image, start_trial, and get_account without opening any schema.

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?

Explicitly routes to alternatives: 'Use fulfil_image instead when the buyer already has credits or already owns the image, and start_trial when they have none and have not tried the store.' It also states when the tool refuses (already owns image or subscription) and the trial-file exception, leaving little to inference.

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