Skip to main content
Glama

Ace 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.6/5.0
Behavior4/5

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

Annotations already state readOnlyHint=false, destructiveHint=false, openWorldHint=true, idempotentHint=false, but the description adds genuinely new behavior: no charge occurs here, the payment happens on a Stripe-hosted page, and the caller must redirect the buyer to continue_url. That is exactly the context an agent needs to avoid misusing a non-destructive mutation. It stops short of saying that repeat calls create separate checkout sessions, which the non-idempotent hint suggests.

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, zero filler, with the action and the required follow-up (redirect to continue_url) front-loaded. Nothing could be cut without losing information.

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?

With no output schema, the description correctly explains the one meaningful return value (continue_url) and even clarifies the no-charge semantics. The remaining gap is parameter explanation for a 0%-coverage schema, not missing return or safety context.

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 the parameter meaning, and it largely does not. "One offer" hints that offer_id is the sole product selector, but the two enum values and the quantity parameter (which is capped at 1) are never explained, so an agent learns nothing about what quantity does or why it is capped.

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?

"Start a purchase of one offer" gives a specific verb (start/create a checkout) and resource (purchase of an offer), and the mention of a Stripe-hosted checkout page pins down the mechanism. It does not explicitly distinguish itself from the sibling get_checkout, but the create-vs-fetch split is inferable from the verb.

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?

The description implies the trigger (a buyer wants to purchase an offer) and instructs what to do with the result (send the buyer to continue_url), which is useful implied usage. It never names get_checkout or any alternative, and gives no prerequisites or when-not-to-use conditions.

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