Skip to main content
Glama

BRAINIAC Inventory Intelligence

Calculate stockout risk

inventory-intelligence_stockout-risk-calculate

Compare available stock with the calculated reorder point from supplied demand and lead times. Risk is not calculated when lead time or demand history is missing. Price $0.05 USDC. POST /api/v1/inventory-intelligence/stockout-risk-calculate. 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_stockout-risk-calculate"
  }
}

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

B3.4/5.0
Behavior4/5

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

With no annotations, the description still discloses concrete operational facts: a $0.05 USDC cost, a 402 payment gate that prevents execution, and a defined no-result condition when inputs are absent. It does not state whether the calculation has side effects or what the response contains, leaving some behavioral burden uncovered.

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 sentence, followed by the precondition, then pricing and transport details. Four short sentences with no filler, though the bare endpoint path and 402 note are somewhat operational-metadata-ish.

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?

Covers what the tool computes, its cost, and its failure gating, which is meaningful for a paid endpoint. However, for a 16-parameter tool with nested objects, multiple interchangeable input formats, and no output schema, the description leaves an agent without enough to construct a correct call.

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?

Schema description coverage is 0% across 16 parameters including nested file, products, sales, suppliers and purchases objects. The description only gestures at 'demand', 'lead times' and 'available stock' and never maps them to parameters or explains the four alternative input channels (csv, json, text, file).

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?

States a specific verb and resource: compares available stock against a calculated reorder point. It implies its position downstream of the reorder-point and safety-stock tools but never names them, so sibling differentiation is left implicit.

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

Usage Guidelines3/5

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

Gives one useful precondition — no risk is produced when lead time or demand history is missing — which tells the agent what inputs are mandatory even though required is empty. It offers no explicit when-to-use-vs-alternatives guidance against reorder-point-calculate or safety-stock-calculate.

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