Skip to main content
Glama

AIFEC

checkout_review

Read-only

The exact order that would be placed: lines, discounts, shipping, taxes, the total (total_cents and total formatted), the delivery address and the payment method, and the confirm_token that checkout_place needs. Read the total from here: never calculate it. If something is missing it says what. When no API key with the scope orders:create is sent, the shop emails a 6-digit verification code to the buyer for security and says so in "confirmation": tell the person, ask for the code and wait for it.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "checkout_review"
  }
}

Input Schema

NameRequiredDescriptionDefault
session_idNoOnly if your client does not keep the MCP session (the Mcp-Session-Id header): the session_id that an earlier answer of this server gave you. It keeps the same cart between calls.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

With only readOnlyHint=true supplied, the description carries real weight and delivers: it discloses the full return payload despite there being no output schema, states that missing data is reported back rather than silently dropped, and — most valuably — describes the auth-dependent side effect where an email verification code is sent and a 'confirmation' field appears, with instructions to pause for human input. None of that is inferable from the annotations or schema.

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 critical information (what it returns, where the authoritative total lives) is front-loaded and no sentence is filler. The structure is dense and colon-chained, reading as a run-on, but each clause carries distinct operational content rather than restating the name.

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 preview tool with no output schema, the description compensates by enumerating every returned field, covering the error case, and documenting the two distinct auth paths including the required human-in-the-loop step. An agent has everything needed to call it and to interpret either response shape.

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 a single optional parameter (session_id) at 100% schema description coverage, so the schema already explains its purpose and cart-persistence semantics. The description adds no additional meaning about session_id. This is the baseline case where structured fields do the work.

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 opens with 'The exact order that would be placed' and enumerates exactly what is returned (lines, discounts, shipping, taxes, totals, address, payment method, confirm_token), which unambiguously reads as a pre-placement preview. It also ties itself to the sibling checkout_place by naming the confirm_token that tool needs. It stops just short of 5 because no explicit verb ('preview'/'review without placing') appears — the operation is inferred from the resource description and the tool name.

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 concrete directive — 'Read the total from here: never calculate it' — and implies the correct sequencing by naming checkout_place as the consumer of confirm_token. It also prescribes an exact procedure for the unauthenticated case (tell the person, ask for the code, wait). There is no explicit 'do not call this when...' exclusion, so it falls short of the full 5.

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