Skip to main content
Glama

Prepare checkout link

prepare_checkout
Idempotent

Get a cart ready for checkout. Re-checks that everything is still available for the date and that the cart meets that date's minimum, then returns the items, the price breakdown (delivery, fees, tax, total, deposit due today), what the customer still has to enter, and handoff_url: a private link that opens this exact cart at checkout on any phone or computer. This tool never pays or places the order: the customer pays on that page, or, once they have authorized it, you complete checkout there for them. Give handoff_url to the customer only.

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": {
      "cart_id": "<cart_id>"
    },
    "name": "prepare_checkout"
  }
}

Input Schema

NameRequiredDescriptionDefault
cart_idYesThe cart_id from add_to_cart

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

The description adds substantial behavior beyond the annotations: it re-checks availability and minimums, returns a detailed price breakdown, and explicitly says it never pays or places the order. It also gives a security-sensitive instruction to share handoff_url only with the customer.

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?

The description is front-loaded with the core action, then details returns and the important non-payment boundary. Despite being fairly rich, every part supports correct invocation or safe handoff.

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?

There is no output schema, but the description explains the returned items, price breakdown, remaining customer inputs, and handoff_url. Combined with annotations covering safety and idempotency, this is complete enough for an agent to call and use the tool 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?

There is only one parameter and the schema already documents cart_id fully, including that it comes from add_to_cart. The description does not add further meaning about cart_id beyond the schema, so the baseline is appropriate.

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?

The description states a specific verb and resource: getting a cart ready for checkout. It also clarifies the outcome, a checkout handoff link and price breakdown, which separates it from cart-building, quoting, fee, and product-info siblings.

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?

It clearly establishes the usage context: prepare a cart for checkout and give the customer the handoff_url. It also states the tool never pays or places the order, which is an important boundary, but it does not explicitly name when to use a sibling such as build_quote instead.

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