Skip to main content
Glama

AIFEC

checkout_status

Read-only

Where the purchase is: what is still missing (contact, address, shipping, payment, in the order to ask for it), the cart summary and what is already saved. Personal data come masked. Call it before asking the customer anything about their order.

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_status"
  }
}

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

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description still contributes real behavioral context beyond that: personal data is returned masked, and the missing items are conveyed in the order they should be asked about, which shapes downstream agent behavior rather than just describing output.

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?

It is front-loaded with the core answer ("Where the purchase is") followed by an enumerated breakdown of what is included, so the agent can stop reading early. The parenthetical list is a bit dense and the sentence runs long, but no sentence is wasted.

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?

There is no output schema, so the description carries the burden of describing return content, and it does so across missing-step enumeration, cart summary, saved data, and masking. It is slightly thin on edge cases such as an empty or nonexistent cart, which would matter for a read used at the start of every flow.

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 single session_id parameter is fully documented in the schema, including the fallback case where no Mcp-Session-Id header is present and the guarantee that the cart persists between calls. The description adds nothing on parameters, which is acceptable given 100% coverage but earns no extra credit.

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 states concretely what the tool returns: the purchase state, what is still missing across contact/address/shipping/payment, the cart summary, and what is already saved. That is far more specific than a bare restatement of the name. It does not, however, differentiate itself from close siblings like checkout_review or cart_view, leaving the agent to infer the boundary.

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?

"Call it before asking the customer anything about their order" gives a clear triggering condition tied to agent workflow. There are no explicit exclusions or named alternatives, so the guidance is clear context without routing rules.

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