Skip to main content
Glama

AIFEC

checkout_place

Place the order. Needs the confirm_token of the last checkout_review, buyer_confirmed true (you declare that the person has seen the total and said yes) and one of two things: buyer_code, the 6-digit verification code that the shop emails to the buyer when you call checkout_review (ask the person for it and wait: never guess it), or an API key with the scope orders:create, sent as Authorization: Bearer. Without them nothing is placed. If anything changed after the review, the confirm_token is no longer valid: review again. The person pays: the answer says how.

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": {
      "confirm_token": "<confirm_token>",
      "buyer_confirmed": "<buyer_confirmed>"
    },
    "name": "checkout_place"
  }
}

Input Schema

NameRequiredDescriptionDefault
buyer_codeNoThe 6-digit code the shop emailed to the buyer after checkout_review. Not needed with an API key that has the scope orders:create
confirm_tokenYesThe confirm_token of the last checkout_review
buyer_confirmedYestrue: the person has seen the total and said yes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

The single annotation only tells us readOnlyHint=false. The description supplies what the annotation cannot: the auth scheme (Authorization: Bearer with orders:create scope), the hard failure mode ("Without them nothing is placed"), the token-invalidation rule, and the instruction never to guess the emailed code but to ask the person and wait. It even hints that the response explains payment.

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 action and its blocking preconditions are front-loaded, and the closing line about payment is terse and useful. Some sentences are long and clause-heavy (the buyer_code/API-key alternative), but nothing is filler.

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?

For a three-parameter mutating commit tool with no output schema, this covers the prerequisite chain, both credential paths, the failure consequence, and the recovery action. Nothing needed to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the text adds meaning the schema does not: that buyer_confirmed is an assertion the agent makes on the person's behalf, and that an invalidated confirm_token requires returning to checkout_review rather than retrying. Most parameter detail (6-digit code, scope requirement) does restate the schema, keeping it below a 5.

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?

"Place the order" is a specific verb plus resource, and the text immediately positions it relative to checkout_review (which produces the confirm_token it consumes). An agent can tell this is the terminal commit step of the checkout flow, not a review or a payment-setup call.

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

Usage Guidelines5/5

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

It states the preconditions (confirm_token from the last checkout_review, buyer_confirmed true, plus one of buyer_code or an orders:create API key) and a when-not: if anything changed after the review the token is void and you must review again. It also names the alternative path (API key instead of buyer_code) explicitly.

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