Skip to main content
Glama

Checkout link

start_checkout
Read-onlyIdempotent

For online stores on Shopify: a link that opens the store’s own cart with the chosen products in the customer’s browser, with the total. The store confirms stock and the final price at checkout; nothing is ordered or charged by this tool. Other businesses answer with how to buy.

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": {
      "business": "<business>",
      "items": "<items>"
    },
    "name": "start_checkout"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYes
businessYesThe business id from find_businesses, e.g. "carat-story".

Output Schema

NameRequiredDescriptionDefault
noteYes
itemsNo
totalNo
reasonNo
chat_urlNo
currencyNo
how_to_buyNo
checkout_urlYes
whatsapp_urlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the annotations, the description explains that the link opens the store's own cart in the customer's browser, that stock and final price are confirmed by the store, and that nothing is ordered or charged by this tool. It does not cover link expiry, authentication requirements, or rate limits, so it is informative but not exhaustive.

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?

The description is three sentences, front-loads the Shopify applicability, and includes only relevant caveats about ordering and charges. The first sentence is slightly awkward as a noun phrase, but there is no unnecessary wording.

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?

For a relatively simple read-only link-generation tool with an output schema and safety annotations, the description covers the essential behavior: what the link does and that no purchase occurs. It omits prerequisites and link lifecycle details, but the structured fields cover most remaining needs.

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?

The description adds some meaning by framing items as 'chosen products' and noting that the total is included in the cart. With only 50% schema description coverage, it does not fully compensate for gaps around the business parameter, quantity limits, and product/variant selection details.

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 clearly states that this tool provides a Shopify cart/checkout link containing chosen products and a total, which is specific enough to understand its purpose. It distinguishes Shopify online stores from other businesses, but it does not explicitly use a verb like 'returns' or directly differentiate against named 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 gives a clear applicability condition ('For online stores on Shopify') and an exclusion ('Other businesses answer with how to buy'). However, it does not name the alternative tool for non-Shopify businesses or state prerequisites such as finding the business/product IDs.

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