Skip to main content
Glama
stablevoy-mcp

stablevoy-mcp

Official

Read the payment page steps of an invoice

get_checkout_trail
Read-onlyIdempotent

Retrieves an invoice's chronological checkout steps and timestamps so you can identify where a buyer stopped in the payment flow.

Instructions

Gets the steps one invoice went through, oldest first, each with the time it was first reached. Needs a store key (npx stablevoy-mcp login). The steps are created, what the payment page reported (opened with page or widget, option_changed, details_copied, wallet_started, wallet_rejected, wallet_failed, tx_sent), the first payment seen (detected) and the outcome (paid, expired or cancelled). Use it to see where a buyer stopped. A buyer who pays from another device skips page steps. Without store every connected store is asked; an id no store has gives not_found. Use get_checkout_funnel for the counts of a period and get_invoice for the payments. A failure comes back as an error with its code and what to do, for example rate_limited with the seconds to wait.

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": {
      "invoiceId": "<invoiceId>"
    },
    "name": "get_checkout_trail"
  }
}

Input Schema

NameRequiredDescriptionDefault
storeNoStore id or exact store name from list_stores. Needed only when several stores are connected.
invoiceIdYesThe invoice id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.9.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description still adds real behavior: the store-key auth requirement, the fallback of querying every connected store when no store is given, the not_found result for an unknown id, the caveat that a buyer paying from another device skips page steps, and the error envelope (code plus remedy, e.g. rate_limited with seconds to wait). These are exactly the operational facts annotations cannot carry.

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 core behavior and the ordering guarantee are front-loaded, and every sentence carries information. The long parenthetical step list makes the middle dense and slightly run-on, but nothing is redundant enough to cut without losing real content.

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, yet the description effectively documents the return shape — ordered steps with first-reached timestamps, the possible step values, and the terminal outcome. Combined with the error-handling note and the multi-store fallback, an agent has everything needed to call it and interpret the response.

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 the baseline would be 3, but the description adds meaning beyond the schema by explaining what omitting `store` does (all connected stores queried) and what an unrecognized store id produces (not_found). It does not add syntax detail for invoiceId, but that parameter is a UUID already fully specified in the schema.

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?

The description opens with a specific verb and resource ('Gets the steps one invoice went through, oldest first') and enumerates the actual step values (created, opened, option_changed, wallet_failed, tx_sent, detected, paid/expired/cancelled). That is far more than the title restated — an agent knows exactly what data comes back and in what order.

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 use case ('Use it to see where a buyer stopped') and explicitly routes to alternatives with their conditions: get_checkout_funnel for period counts, get_invoice for payments. Exclusions are handled implicitly by those contrasts, so the agent has a clear decision rule.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.