Skip to main content
Glama
storelink-mcp

storelink-mcp

by jaredalonzo

MCP tools decision

Public Tools

server.py

  • list_store() > read only -- agent tool to determine which stores are available to access

  • raise_replenishment_order() > write -- provide the agent the capability to place orders on behalf of Korral

  • replenishment_order_status() > read only -- agent tool to determine the status of a placed order

  • sku_report() > read only -- agent tool to assess sku information, including supplier and lead time

Related MCP server: korral-mcp

Utility private functions (not agent tools)

server.py

  • sku_lead_time() > read only (private) -- utility tool for the sku_report public tool to determine how fast an order can be fulfilled.

  • stock_report(sku) > read only (private) -- compare what is in stock/on-hand vs recent post transactions for the sku

Observability

Package in observability/

1. Technical trace — for support / engineers

Structured JSON on the storelink_mcp.trace.technical logger, meant for diagnosing issues as they happen:

  • Explicit MCP server version (mcp_server.name + version) on every record.

  • Correlation trace_id (shared with the audit stream) and the MCP request_id.

  • Tool name and business arguments (the audit-only reason is stripped out).

  • Per-leg downstream spans — every StoreLink HTTP call with method, path, status, latency, and retry attempts, tagged leg: "mcp<->storelink".

  • On failure: the failing connection leg (duvo<->mcp vs mcp<->storelink), the unwrapped root-cause error type/message (FastMCP wraps tool errors in a ToolError; the original StoreLinkAPIError is surfaced with wrapped_by), and the full chained stack trace.

2. Audit trace — for buyers (non-technical stakeholders)

A readable line on the storelink_mcp.trace.audit logger:

  • A plain-English description of each step the agent took.

  • The agent's reasoning, captured via an optional reason argument added to every public tool (the model is instructed to always provide it).

  • A buyer-friendly outcome — a summary of the result on success, or a calm "this step could not be completed" note on failure (never a stack trace).

  • A running step_number so the actions read in order.

Keys transactions

Each StoreLink API key (X-Korral-Store-Key) is scoped to one store id.

There are two scenarios to consider per the assessment brief: a) key rotates mid-flight and b) unknown store id is referenced.

-- For a, when a key is rotated while a request is in flight e.g. storelink api returns 40x errors, invalidate the currently stored key, reload with the newly rotated key, and retry (max 3).

-- For b, when a new or unknown store is provided, before making any request to the storelink API, inform the end user (buyer) that the store number referenced is not included in the available stores, provide them explicit written instructions to ask the Korral IT team to provision a key for the store provided.

Shipping

-- Where this runs: The MCP server will run in Korall's GCP instance via GCP Cloud Run where all the data is already internal/private. Assuming that StoreLink API also exists in the same GCP instance, all the data that comes into the MCP server is also internal/private.

-- How it gets there: The MCP server will be built as a docker image that Duvo maintains and ships out to Korral for verification before they deploy new builds/changes done by Duvo.

-- How secrets are handled: see Keys transactions section

Available Tools

4 tools
list_storeA

List the stores this account can access (id, name, address, timezone).

Inputs: reason.

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.

Inputs: sku (required), quantity (required), store_id (required), note, +1 more.

replenishment_order_statusA

Get the current status of a previously raised replenishment order.

Inputs: order_id (required), store_id (required), reason.

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.

Inputs: sku (required), store_id (required), reason. Returns: object

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.9/5.0

    Scored across 4 tools

    Disambiguation5/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      MCP server that lets a Duvo agent talk to Korral's StoreLink API, enabling category buyers to offload daily stock checking, replenishment ordering, and order tracking tasks.
      -
    • F
      license
      A
      quality
      D
      maintenance
      MCP server exposing the StoreLink grocery stocking API as tools for category buyer workflows, including inventory checks and replenishment orders.
      5
      -
    • F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that enables operations teams to diagnose and recover stalled fulfillment orders via tools like retry_fulfillment and escalate_order, with safety boundaries limiting writes to retry and audit operations.
      -