Skip to main content
Glama

rr_list_lost_sales

Read-onlyIdempotent

Retrieve estimated lost sales caused by stockouts over a configurable lookback period, helping sellers quantify missed revenue and prioritize inventory replenishment.

Instructions

Get estimated lost sales due to stockouts.

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_lost_sales"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoLookback days (default 30)
limitNoRows per page (default 50, max 500).
cursorNonext_cursor from the previous page. Pass it with the same other inputs until has_more is false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.3.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description adds one genuinely useful behavioral qualifier: the numbers are 'estimated,' signaling an approximation rather than measured actuals. It says nothing about how the estimate is derived or the pagination semantics of the listing.

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?

A single front-loaded sentence with zero filler or redundancy. It is efficient, though the terseness leaves nothing to disambiguate siblings or hint at result shape.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple, annotation-rich, three-parameter list tool with no output schema, the description is adequate but thin. Because there is no output schema, an agent gets no sense of what a lost-sales record contains or whether results are ranked; the description could have said so in a clause.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so days, limit, and cursor are each fully documented in the schema, including cursor reuse rules. The description adds no meaning beyond that, which is the expected baseline when the schema carries the load.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource: 'Get estimated lost sales due to stockouts.' The stockout qualifier meaningfully separates it from rr_list_sales_history and rr_list_stockout_risks, though it never names those siblings or explains the boundary explicitly.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no stated prerequisites, and no mention of when another tool is more appropriate. For an agent choosing between this and rr_list_stockout_risks or rr_list_slow_movers, the description offers no routing help beyond the noun 'lost sales.'

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