Skip to main content
Glama

Start checkout

checkout_start
Destructive

Start checkout with Dintero or DinteroVipps. Returns a Dintero payment URL and reference; the guest approves the payment on Dintero's page. A zero-amount cart completes immediately. An unchanged cart gets the same payment link back.

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": {
      "storeId": "<storeId>",
      "paymentType": "<paymentType>"
    },
    "name": "checkout_start"
  }
}

Input Schema

NameRequiredDescriptionDefault
storeIdYesOkam store id.
paymentTypeYesDintero or DinteroVipps.

Output Schema

NameRequiredDescriptionDefault
cartNo
orderNo
statusNo
messageNo
providerNo
paymentUrlNo
validationNo
paymentTypeNo
clientSecretNo
paymentReferenceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / cart / properties / items / items / properties / product / properties / allergens / items / properties / code
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations (readOnly=false, destructive=true, openWorld=true) only flag that this mutates external state; the description adds genuinely new behavior: a guest-facing approval page, immediate completion for zero-amount carts, and idempotent return of the same link for an unchanged cart. The notable gap is that it never explains what makes the call 'destructive' — e.g., whether it reserves stock, creates an order, or invalidates a prior reference.

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, front-loaded with the action and providers, followed by return value and then the two edge cases. Every sentence carries distinct information with no filler.

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?

An output schema exists, yet the description still usefully previews the URL/reference return shape, and it covers the zero-amount and repeat-call cases. For a state-mutating, open-world tool it should still say what preconditions the cart must satisfy and what a failed start returns.

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 100%, so the schema already documents both parameters. The description reinforces the narrowing of paymentType to Dintero/DinteroVipps, which is useful given the 20-value enum, but adds nothing about storeId or what happens if a non-Dintero value is passed.

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 ('Start checkout') plus the supported payment providers (Dintero/DinteroVipps) and what it returns (payment URL and reference). It separates itself from the cart_* family by being the flow-launching step, though it never names checkout_verify, the most confusable sibling.

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?

Usage is implied rather than stated: an agent can infer this is called once the cart is ready and that Dintero/DinteroVipps payment types are the supported ones. There is no explicit when-not guidance, no mention of prerequisites such as cart_validate or cart_get, and no routing advice versus checkout_verify or payment_methods_list.

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