Skip to main content
Glama

rr_list_slow_movers

Read-onlyIdempotent

Identify held SKUs that aren't selling, surface dead stock with no sales in 12 months, and review on-hand units, sales in the lookback window, and dead-stock totals.

Instructions

Overstock / dead-stock / slow movers: SKUs you are HOLDING (on-hand > 0) that aren't selling - capital tied up. Returns on_hand, units sold in the window, and a dead_stock flag: held with no sale in the last 12 months, whatever the window (null, with dead_stock_message saying why, while the sales history is too short to decide). dead_stock_summary is the seller's total dead-stock count across every store, whatever store_id asks for, and its value at cost when costs may be shown. Inventory-first, so never-sold dead stock is surfaced too. total is how many held SKUs there are; has_more is true when that is more than the page returned.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "rr_list_slow_movers"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoLookback window in days (default 30, max 90)
limitNoNumber of slow movers per page (default 20, max 500).
cursorNonext_cursor from the previous page. Pass it with the same other inputs until has_more is false.
store_idNoOnly sales from this store.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.3.1

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent annotations by disclosing a non-obvious behavior: dead_stock_summary is the seller-wide count across every store regardless of store_id, and value is shown only when costs may be shown. It also explains pagination semantics (total = number of held SKUs, has_more = more than the page) and the short-history escape hatch via dead_stock_message.

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?

Purpose is front-loaded in the first clause and every sentence carries information. The long parenthetical about null and dead_stock_message is dense and takes a second read, costing a point on clarity.

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?

With no output schema, the description still names the returned fields (on_hand, units sold, dead_stock flag, dead_stock_summary, total, has_more) and explains each one's semantics. Nothing an agent needs to call this correctly or interpret the page is missing.

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 baseline is 3, but the description adds real meaning: store_id filters sales only (the summary ignores it) and days does not change the dead_stock determination, only the sales window. Those cross-parameter interactions are not 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?

States a specific verb+resource with a precise qualifying rule: SKUs held with on-hand > 0 that aren't selling. It also defines the sibling-adjacent concepts it covers (overstock, dead stock, never-sold stock) so an agent knows this is the inventory-first view rather than a sales or risk list.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear contextual guidance on when rows appear and how the dead_stock flag is decided ('held with no sale in the last 12 months, whatever the window'), including the null-case fallback. It does not explicitly name alternatives such as rr_list_top_sellers or rr_list_stockout_risks and say when to prefer them, so it stops short of a 5.

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