Skip to main content
Glama

Purchase status

purchase_status
Read-onlyIdempotent

Check a purchase started with start_purchase. Returns its state: awaiting_deposit (send the amount), deposit_seen, processing, paid (the order is recorded and the seller was paid), refunded (funds returned to refund_to), failed, expired (deadline passed without a deposit) or review (being checked by Port66). Also returns links to the buyer's payment and the seller's payout transactions and, once paid, the order_id. Poll every 15 to 30 seconds while the state is awaiting_deposit, deposit_seen or processing. Requires a Port66 session.

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": {
      "checkout_id": "<checkout_id>"
    },
    "name": "purchase_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
checkout_idYesThe checkout_id returned by start_purchase.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / checkout_id / description
      Previous value: -"The checkout_id from start_purchase"New value: +"The checkout_id returned by start_purchase."
  2. First observed

TDQS

A4.3/5.0
Behavior3/5

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

Adds substantial context beyond the readOnly/idempotent annotations: a complete state taxonomy with plain-language meanings (paid means the order is recorded and the seller was paid; refunded returns funds to refund_to; expired means the deadline passed), plus what extras accompany the response (payment and payout links, order_id once paid). However, it does not disclose polling limits, rate limits, or what happens if the checkout_id is unknown or expired long ago, so it is best characterized as helpful rather than complete.

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?

Front-loaded with the action and its source, then the state list, then return extras, then polling cadence and prerequisite. Dense single sentences, but each clause carries decision-relevant information and none 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?

There is no output schema, so the description must carry the return contract, and it does: every state value is defined and the auxiliary fields are named. For a one-parameter read tool with strong annotations, nothing an agent needs in order to call it and interpret the result 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% and the single checkout_id parameter is already self-documenting, so the baseline is 3. The description earns one extra point by tracing provenance ('started with start_purchase'), telling the agent where the identifier comes from rather than only what it is.

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?

Names a specific verb and resource ('Check a purchase') and anchors it to the sibling that creates it ('started with start_purchase'). The state enumeration that follows makes the returned scope unmistakable, so an agent can separate it from start_purchase or offer_status without opening a schema.

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 explicit operational guidance: poll every 15-30 seconds while the state is awaiting_deposit, deposit_seen or processing, and notes a Port66 session is required. It does not state what to do when the state reaches a terminal value or how to distinguish this from non-purchase status checks, so it stops short of full when/when-not coverage.

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