Skip to main content
Glama

Create checkout link

create_checkout_link
Read-onlyIdempotent

Quote an order (one or more products, 1-10 vials each) and get the checkout link the buyer opens to pay. Nothing is charged or reserved until the buyer pays on that page.

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": {
      "country": "<country>",
      "items": "<items>"
    },
    "name": "create_checkout_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYes
countryYesCountry of the BUYER: US (United States, prices in USD). It is the only market served.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / country / description
      Previous value: -"Country of the BUYER: AR (Argentina, prices in ARS) or US (United States, prices in USD)."New value: +"Country of the BUYER: US (United States, prices in USD). It is the only market served."
    • changedInput schema / properties / country / enum
      Previous value: -[
      -  "AR",
      -  "US"
      -]New value: +[
      +  "US"
      +]
  2. 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=true, idempotentHint=true and destructiveHint=false, and the description usefully explains WHY that is safe: nothing is charged or reserved until the buyer pays. That is genuine added context for an agent worried about triggering a financial side effect. It stops short of covering link expiry or whether repeated calls yield the same link.

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?

Two sentences, front-loaded with the action and result, closing with the safety caveat. No filler and nothing repeated.

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 two-parameter tool with no output schema, the description tells the agent what it gets back (a checkout link the buyer opens) and what does not happen (no charge, no reservation). Only the link's lifespan and reuse behavior are left unstated.

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 coverage is only 50% (items and vials lack descriptions), so the description has to compensate. It does partially: 'one or more products' and '1-10 vials each' restate the minItems and min/max constraints in plain language, but it adds nothing about the items structure or quantity semantics beyond what the schema already encodes.

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?

States a specific verb-and-resource pair (quote an order, get a checkout link) plus scope (one or more products, 1-10 vials each). It is unmistakably different from list_products and store_info, so an agent can select it without opening a schema.

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 commercial scenario it serves is implied clearly (buyer needs a link to pay), but there is no explicit when-to-use guidance and no mention of the prerequisite that product IDs come from list_products. That dependency only surfaces inside the schema descriptions, not in the tool description itself.

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