このMCPでできること
Validates inputs and runs paid inventory reorder analyses using SKU sales, stock and lead-time data.
機能
ツール
4
ツール
get_run
Get run status and results
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.
読み取り専用
冪等
入力スキーマ
{'type': 'object', 'required': ['receipt_id', 'access_token'], 'properties': {'receipt_id': {'type': 'string', 'description': 'receipt_id from start_<bot>, like RG-202610-1A2B3C4D.'}, 'access_token': {'type': 'string', 'description': 'access_token from start_<bot>.'}}, 'additionalProperties': False}
list_bots
List bots
List the bots this server can run: what each one does, its price per run, what a run returns, its input schema, and the names of its validate_ and start_ tools. Free and read-only.
読み取り専用
冪等
入力スキーマ
{'type': 'object', 'properties': {}, 'additionalProperties': False}
start_inventory_reorder
Start a paid Inventory Reorder Snapshot run ($19.00, card checkout)
Start a paid Inventory Reorder Snapshot run ($19.00 per run). This tool never charges anyone; it returns a Stripe checkout link that a person opens and pays. It creates the checkout and returns the link with a receipt_id and access_token. Nothing runs until the person pays on Stripe's page. Show the user the link and the price and ask them to pay; then call get_run with the receipt_id and access_token. Results are also emailed to the address given. Takes the same JSON as validate_inventory_reorder_inputs ({"inputs": {...}, "email": "..."}); run validate_inventory_reorder_inputs first, since invalid inputs are rejected here too. Each call creates a new checkout, so do not retry a call that succeeded.
Returns: A PDF report and a JSON plan: one row per SKU (status, order quantity, days of cover, cash tied up) plus summary totals.
Turns a store's per-SKU sales history, stock on hand, open purchase orders and supplier lead times into a reorder plan: which SKUs to reorder now and how many units (rounded up to MOQ and case pack), which are out of stock or will run out before the next delivery could arrive, which are overstocked or not selling, how much cash is tied up in excess stock, and which SKUs earn the revenue (ABC tiers).
It is rule-based and deterministic, computed only from the figures supplied. It is not a forecast: it does not model seasonality, trend or promotions, multiple locations, variant roll-ups, supplier price breaks or margin. It does not connect to Shopify or any other system; the data is sent inline.
Inputs: an as_of date, an optional window_days (28 to 365, default 90) that units_sold covers, and 1 to 800 SKUs, each with sku, units_sold, on_hand, unit_price and unit_cost. lead_time_days is needed per SKU or in defaults. The whole request must stay under 200 KB.
外部アクセスあり
入力スキーマ
{'type': 'object', 'required': ['inputs', 'email'], 'properties': {'email': {'type': 'string', 'format': 'email', 'description': "The buyer's email: Stripe sends the payment receipt there and botx402 emails the results link."}, 'inputs': {'type': 'object', 'required': ['as_of', 'skus'], 'properties': {'skus': {'type': 'array', 'items': {'type': 'object', 'required': ['sku', 'units_sold', 'on_hand', 'unit_price', 'unit_cost'], 'properties': {'moq': {'type': 'integer', 'maximum': 1000000000, 'minimum': 1, 'description': 'Minimum order quantity. An order below it is raised to it.'}, 'sku': {'type': 'string', 'maxLength': 64, 'minLength': 1}, 'title': {'type': 'string', 'maxLength': 200}, 'on_hand': {'type': 'integer', 'maximum': 1000000000, 'minimum': 0}, 'on_order': {'type': 'integer', 'maximum': 1000000000, 'minimum': 0, 'description': 'Units on open purchase orders. Assumed to arrive after lead_time_days.'}, 'unit_cost': {'type': 'number', 'minimum': 0}, 'unit_price': {'type': 'number', 'minimum': 0}, 'units_sold': {'type': 'integer', 'maximum': 1000000000, 'minimum': 0, 'description': 'Net units sold in the window (after returns).'}, 'safety_days': {'type': 'integer', 'maximum': 365, 'minimum': 0}, 'lead_time_days': {'type': 'integer', 'maximum': 365, 'minimum': 0}, 'order_multiple': {'type': 'integer', 'maximum': 1000000000, 'minimum': 1, 'description': 'Case pack. Order quantities are rounded up to a multiple of it.'}, 'days_out_of_stock': {'type': 'integer', 'maximum': 365, 'minimum': 0, 'description': 'Days in the window the SKU had no stock. Missing means 0. Cannot exceed window_days.'}, 'target_cover_days': {'type': 'integer', 'maximum': 365, 'minimum': 1}}, 'additionalProperties': False}, 'maxItems': 800, 'minItems': 1}, 'as_of': {'type': 'string', 'format': 'date', 'description': 'Last day covered by the sales figures (YYYY-MM-DD). Echoed in the report.'}, 'currency': {'type': 'string', 'pattern': '^[A-Z]{3}$', 'description': 'ISO currency code for prices and costs. Display only. Defaults to USD.'}, 'defaults': {'type': 'object', 'properties': {'safety_days': {'type': 'integer', 'maximum': 365, 'minimum': 0}, 'lead_time_days': {'type': 'integer', 'maximum': 365, 'minimum': 0}, 'target_cover_days': {'type': 'integer', 'maximum': 365, 'minimum': 1, 'description': 'Days of stock an order should cover on top of lead time and safety days. Defaults to 30.'}}, 'description': 'Fallbacks for SKUs that do not set their own. lead_time_days is required here unless every SKU sets it.', 'additionalProperties': False}, 'window_days': {'type': 'integer', 'maximum': 365, 'minimum': 28, 'description': 'Days of sales history the units_sold figures cover. Defaults to 90 when omitted.'}}, 'additionalProperties': False}}, 'additionalProperties': False}
validate_inventory_reorder_inputs
Validate Inventory Reorder Snapshot inputs
Check inputs for Inventory Reorder Snapshot before asking a human to pay. Free; nothing is charged, stored or run. Takes exactly the JSON start_inventory_reorder takes: {"inputs": {...}}, plus "email" if you have it (checked too, optional here). Returns either valid (with a one-line summary of what will be analysed) or every problem found at once, each with its path (e.g. inputs.skus[2].unit_cost) and how to fix it. Fix them all, call again, then call start_inventory_reorder with the same JSON plus the buyer's email.
Turns a store's per-SKU sales history, stock on hand, open purchase orders and supplier lead times into a reorder plan: which SKUs to reorder now and how many units (rounded up to MOQ and case pack), which are out of stock or will run out before the next delivery could arrive, which are overstocked or not selling, how much cash is tied up in excess stock, and which SKUs earn the revenue (ABC tiers).
It is rule-based and deterministic, computed only from the figures supplied. It is not a forecast: it does not model seasonality, trend or promotions, multiple locations, variant roll-ups, supplier price breaks or margin. It does not connect to Shopify or any other system; the data is sent inline.
Inputs: an as_of date, an optional window_days (28 to 365, default 90) that units_sold covers, and 1 to 800 SKUs, each with sku, units_sold, on_hand, unit_price and unit_cost. lead_time_days is needed per SKU or in defaults. The whole request must stay under 200 KB.
読み取り専用
冪等
入力スキーマ
{'type': 'object', 'required': ['inputs'], 'properties': {'email': {'type': 'string', 'format': 'email', 'description': "The buyer's email: Stripe sends the payment receipt there and botx402 emails the results link."}, 'inputs': {'type': 'object', 'required': ['as_of', 'skus'], 'properties': {'skus': {'type': 'array', 'items': {'type': 'object', 'required': ['sku', 'units_sold', 'on_hand', 'unit_price', 'unit_cost'], 'properties': {'moq': {'type': 'integer', 'maximum': 1000000000, 'minimum': 1, 'description': 'Minimum order quantity. An order below it is raised to it.'}, 'sku': {'type': 'string', 'maxLength': 64, 'minLength': 1}, 'title': {'type': 'string', 'maxLength': 200}, 'on_hand': {'type': 'integer', 'maximum': 1000000000, 'minimum': 0}, 'on_order': {'type': 'integer', 'maximum': 1000000000, 'minimum': 0, 'description': 'Units on open purchase orders. Assumed to arrive after lead_time_days.'}, 'unit_cost': {'type': 'number', 'minimum': 0}, 'unit_price': {'type': 'number', 'minimum': 0}, 'units_sold': {'type': 'integer', 'maximum': 1000000000, 'minimum': 0, 'description': 'Net units sold in the window (after returns).'}, 'safety_days': {'type': 'integer', 'maximum': 365, 'minimum': 0}, 'lead_time_days': {'type': 'integer', 'maximum': 365, 'minimum': 0}, 'order_multiple': {'type': 'integer', 'maximum': 1000000000, 'minimum': 1, 'description': 'Case pack. Order quantities are rounded up to a multiple of it.'}, 'days_out_of_stock': {'type': 'integer', 'maximum': 365, 'minimum': 0, 'description': 'Days in the window the SKU had no stock. Missing means 0. Cannot exceed window_days.'}, 'target_cover_days': {'type': 'integer', 'maximum': 365, 'minimum': 1}}, 'additionalProperties': False}, 'maxItems': 800, 'minItems': 1}, 'as_of': {'type': 'string', 'format': 'date', 'description': 'Last day covered by the sales figures (YYYY-MM-DD). Echoed in the report.'}, 'currency': {'type': 'string', 'pattern': '^[A-Z]{3}$', 'description': 'ISO currency code for prices and costs. Display only. Defaults to USD.'}, 'defaults': {'type': 'object', 'properties': {'safety_days': {'type': 'integer', 'maximum': 365, 'minimum': 0}, 'lead_time_days': {'type': 'integer', 'maximum': 365, 'minimum': 0}, 'target_cover_days': {'type': 'integer', 'maximum': 365, 'minimum': 1, 'description': 'Days of stock an order should cover on top of lead time and safety days. Defaults to 30.'}}, 'description': 'Fallbacks for SKUs that do not set their own. lead_time_days is required here unless every SKU sets it.', 'additionalProperties': False}, 'window_days': {'type': 'integer', 'maximum': 365, 'minimum': 28, 'description': 'Days of sales history the units_sold figures cover. Defaults to 90 when omitted.'}}, 'additionalProperties': False}}, 'additionalProperties': False}
履歴
最近のツール変更
追加
get_run
2026年10月5日2:40
追加
start_inventory_reorder
2026年10月5日2:40
追加
validate_inventory_reorder_inputs
2026年10月5日2:40
追加
list_bots
2026年10月5日2:40
関連MCP
類似のMCPサーバー
AdButler
com.adbutler/mcp-server
Manages AdButler advertisers, campaigns, ad items, audiences, zones, creatives, catalogs, and advertising reports.
Duvo MCP
io.github.duvoai/duvo
Provides governed retail and CPG operations for cases, queues, approvals, automations, process documentation, integrations, and a…
独行录 / opcmenu
io.github.yzlee/opcmenu
Supports founder and company discovery, collaboration goals and tasks, events and signups, networking, messaging, profiles, produ…
Lovie Company Formation
co.lovie/company-formation
Supports company formation and business administration with bank accounts, cards, invoicing, bookkeeping, accounting periods, and…
freedom-mcp
com.getfreedomos/freedom-mcp
Supports company operations through commitments, teams, agents, customer evidence, leads, content workflows, spreadsheets, commer…
Meta Council
com.meta-council/decision-intelligence
Provides governed workflows for consulting, outreach, sales deals, invoices, marketing campaigns, content approvals, accounting a…
Physical Capability Cloud
network.capability/physical-capability-cloud
Registers and manages physical equipment and operators, supports capability pricing, job contracts, telemetry, verification evide…
synter-ads
io.github.Synter-Media-AI/synter-ads
Manages cross-platform advertising campaigns, audiences, tracking, creative, landing pages, campaign audits, technology intellige…