Skip to main content
Glama

Black Label Bots Website MCP

create_checkout

Start a purchase of one offer. Returns a continue_url: send the buyer there to pay on the Stripe-hosted checkout page. This tool does not charge anything.

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

Input Schema

NameRequiredDescriptionDefault
offer_idYes
quantityNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare the non-read-only, non-destructive, non-idempotent, open-world profile, and the description adds genuinely useful context on top: nothing is charged here, payment is delegated to Stripe, and the caller must act on the returned continue_url. It stops short of covering session lifetime or whether repeated calls create duplicate checkout sessions, which matters given 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, all front-loaded: what it does, what it returns and what to do with it, then a scope disclaimer. No filler or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter tool with no output schema, the description covers the outcome (continue_url) and the side-effect boundary (no charge), which is the critical piece. It is still incomplete on quantity semantics and on what happens if the call is retried or the returned URL expires.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry parameter meaning and it does not. 'One offer' loosely maps to offer_id (whose enum is self-explanatory), but quantity (1-20, default 1) is never explained — whether it means seats, licenses, or units — leaving half the parameters opaque.

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 opens with a specific verb+resource, 'Start a purchase of one offer', and immediately names the artifact it returns (continue_url) and where payment happens (Stripe-hosted checkout page). That is enough to distinguish it from get_checkout and list_products, though it never names the complementary retrieval tool explicitly.

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?

It gives a downstream usage instruction ('send the buyer there to pay') but no guidance on when to call this versus get_checkout or list_products, nor any preconditions such as needing a valid offer or an existing customer. Usage is implied by the checkout flow rather than stated.

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