Inventory reorder plans from SKU sales, stock and lead times. $19 a run, paid by card.
Scored across 2 tools
get_run retrieves results for an existing run, while list_bots enumerates available bots and their schemas. These are clearly distinct read-only operations with no overlapping purpose, so an agent can easily tell them apart.
Both tools follow a consistent snake_case verb_noun pattern: get_run and list_bots. The convention is predictable and readable, matching the start_ and validate_ prefixes referenced in the descriptions.
Only two tools are exposed, which is too thin for a server whose own descriptions reference start_ and validate_ tools that are absent. An agent cannot initiate a run or validate inputs, so the surface does not earn its scope.
The descriptions explicitly mention start_ and validate_ tools that are not in the tool list, leaving no way to launch a run or validate inputs. The lifecycle is broken: list_bots exposes bots, but get_run can only be used after some missing start_ tool has run, making the surface severely incomplete.
Check a run started with a start_ tool and fetch its results. Needs the receipt_id AND the access_token that start_ returned: the token is the proof that the caller started the run, and without it nothing is returned. Status is awaiting_payment (the user has not paid yet), running, completed or failed. When completed, structuredContent.result is the bot's full JSON result, ready to act on, and pdf_url links the PDF report (presigned, expires after 7 days). Free and read-only; poll about once a minute.
Inputs: receipt_id (required), access_token (required).
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Demand forecasts, reorder points, order quantities and inventory health for Shopify stores.
Calculate a SKU reorder point, stock coverage and replenishment quantity from your own assumptions.
Find the cash trapped in your inventory, then size reorder points, safety stock and EOQ.
Safety-stock & reorder planning, FBA-vs-FBM decision, and inventory health audit for sellers
Add one secure layer between your agents and this server.
