Skip to main content
Glama

BRAINIAC Inventory Intelligence

Detect slow-moving stock

inventory-intelligence_slow-moving-stock-detect

Flag SKUs whose supplied unit sales over the disclosed lookback are at or below the slowUnits threshold. Price $0.04 USDC. POST /api/v1/inventory-intelligence/slow-moving-stock-detect. Unpaid calls return 402 and do not run.

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": "inventory-intelligence_slow-moving-stock-detect"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNo
asOfNo
fileNo
jsonNo
textNo
salesNo
productsNo
slowDaysNo
purchasesNo
slowUnitsNo
suppliersNo
reviewDaysNo
historyDaysNo
forecastDaysNo
serviceLevelZNo
excessDaysCoverNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations, the description does real work: it discloses cost ($0.04 USDC), the payment gate (402 on unpaid calls, no execution), and the POST endpoint. It also implies the tool operates on caller-supplied sales data rather than fetching it. It omits, however, what any returned flags look like, how the various input carriers relate, and any rate/limit behavior.

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?

Three tight sentences, front-loaded with the decision rule before the pricing and transport details, with no filler. Slight deduction because the transactional metadata occupies space that could have gone to the unaddressed parameter semantics.

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

Completeness2/5

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

For a 16-parameter tool with nested objects, no annotations, and no output schema, this is thin. The description never explains how to supply data (array vs. inline text vs. file), how sku keys join across datasets, or what the response contains, which is the minimum needed to call it confidently.

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

Parameters2/5

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

Zero of the 16 parameters have schema descriptions, so the description must carry the burden and it covers only slowUnits by name and gestures at a lookback. The mutual exclusivity of csv/json/text/file and how sales, products, purchases, and suppliers combine is completely unaddressed, as are slowDays, reviewDays, historyDays, forecastDays, excessDaysCover, and serviceLevelZ.

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?

Names a specific verb ("Flag") and resource (SKUs) plus the exact decision rule (supplied unit sales at or below slowUnits over the lookback). This separates it from generic inventory tools, but it never distinguishes itself from the equally plausible sibling excess-detect, which an agent could confuse with slow-moving logic.

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?

The description states the flagging criterion but gives no guidance on when to choose this over the other seven inventory siblings, no prerequisites, and no exclusions. An agent must infer from the title alone that this is for dead/obsolete stock detection versus excess or stockout risk.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources