storelink-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_storeA | List the stores this account can access (id, name, address, timezone). |
| sku_reportA | Consolidated reorder report for a SKU at a store. Combines SKU details, current on-hand stock, recent POS demand, and the supplier's lead time so you can judge whether — and how urgently — to replenish. Use this before raising a replenishment order. |
| raise_replenishment_orderA | Place a replenishment order for a SKU at a store, on behalf of Korral. Returns the created order, including its order_id and status. This is a write action — confirm the quantity is intended before calling. |
| replenishment_order_statusA | Get the current status of a previously raised replenishment order. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool targets a distinct operation: listing stores, generating a replenishment report, raising an order, and checking order status. No functional overlap, and descriptions clearly separate their purposes.
All tools use clear, descriptive names, but the pattern is not uniform: 'list_store' and 'raise_replenishment_order' follow verb_noun, while 'replenishment_order_status' and 'sku_report' are noun phrases. This minor inconsistency does not hinder understanding.
With 4 tools, the server is well-scoped for the domain of store replenishment. Each tool serves a necessary step in the workflow without redundancy or bloat.
The tools cover the core replenishment workflow: viewing store info, assessing stock via the SKU report, placing an order, and checking its status. A tool to list past orders or cancel/update orders would improve coverage, but the current set is functional for basic tasks.