Skip to main content
Glama

Prepare checkout

create_checkout
Idempotent

Use this when the person pays for the book themselves. Prepares a Stripe checkout link for the book, using the bookToken. The book does not need to be saved first. Stripe collects their email, delivery address and payment; no charge occurs until they confirm there. Collect the destination country first. Reuse idempotencyKey on retry.

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": {
      "bookId": "<bookId>",
      "bookToken": "<bookToken>",
      "country": "<country>",
      "idempotencyKey": "<idempotencyKey>"
    },
    "name": "create_checkout"
  }
}

Input Schema

NameRequiredDescriptionDefault
bookIdYes
countryYes
quantityNo
bookTokenYes
idempotencyKeyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=true. The description adds real behavioral context beyond that: Stripe collects email/address/payment, no charge occurs until confirmation, and the book need not be saved first. It reinforces the idempotency hint with a concrete retry instruction, though it doesn't say what is returned or whether the link expires.

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?

Six short sentences, zero filler, front-loaded with the selection condition followed by behavior and then operational constraints. Every sentence contributes a distinct piece of 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 should say what the caller gets back; it says a checkout link is prepared but never states the return shape, expiry, or how to hand the link to the user. Otherwise it covers prerequisites, external handoff, charge timing, and retry semantics well for a five-parameter tool.

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 0%, so the description must carry parameter meaning. It explains bookToken's role, why country is needed, and how to use idempotencyKey on retry, but leaves bookId and quantity completely unexplained — a notable gap at five parameters.

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?

States a specific verb and resource: 'Prepares a Stripe checkout link for the book.' The opening clause 'when the person pays for the book themselves' implicitly separates it from pay_book/quote-style siblings, but no sibling is actually named, so differentiation depends on inference.

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

Usage Guidelines4/5

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

Gives a clear usage condition ('when the person pays for the book themselves') and a sequencing prerequisite ('Collect the destination country first'). It does not name an alternative tool or state an explicit when-not, so the agent must infer which sibling handles other payment paths.

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