Skip to main content
Glama

Check an order

checkout_status
Read-onlyIdempotent

Where an order you opened stands, and what each answer MEANS for the money. Funded but not yet acted on = it sits in escrow and is still the buyer's. Completed = the buyer acted from their mail and the shop has been paid. Gone home = the buyer declined and it is back with them. Expired = the hold lapsed unfunded; money that landed after the window closed gets no automatic hand-back yet, and that is being built. Read live off the shop's rail: whether the hold is funded, whether the buyer completed it from their mail (the order shows paid and any download unlocks), whether it was refunded to them instead, or whether it lapsed unfunded. Pass the shop and the order reference checkout_intent returned. This reads state and moves nothing — poll it after your human says they clicked the mail, then hand them the receipt.

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": {
      "shop": "<shop>",
      "order_ref": "<order_ref>"
    },
    "name": "checkout_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
shopYesthe shop's slug
order_refYesthe order reference from checkout_intent, e.g. 'ord_…'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, and the description adds substantial context: it reads state and moves nothing, reads live from the shop's rail, and explains the meaning of each status including the expired-funding caveat. This goes well beyond the structured annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The key purpose is front-loaded, but the description is lengthy and repeats the same status states in two passes (plain-language meanings, then a paraphrased live-read list). It is informative but could be tightened without losing meaning.

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?

With no output schema, the description carries the burden of explaining return states and does so thoroughly, including money implications and the expired/unfunded edge case. It is nearly complete, though it does not describe the raw response shape or any pagination/error behavior.

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% and both parameters are already documented, including that order_ref comes from checkout_intent. The description reinforces the shop slug and order reference origin but adds little syntax or format meaning beyond the schema, so the baseline 3 is appropriate.

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 resource (an order's status) and scope: where an order you opened stands, read live off the shop's rail. It distinguishes itself from checkout_intent by naming the reference that tool returns and the shop/order_ref inputs needed.

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?

Gives clear usage context: poll it after your human says they clicked the mail, then hand them the receipt, and pass the shop and order reference checkout_intent returned. It does not explicitly state when not to use it or name alternative status/check tools, keeping it below a 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