Skip to main content
Glama

BRAINIAC Inventory Intelligence

Calculate reorder points

inventory-intelligence_reorder-point-calculate

Calculate reorderPoint = averageDailyDemand × (leadTimeDays + reviewDays) + safetyStock from supplied history and lead times. No purchase order is created. Price $0.05 USDC. POST /api/v1/inventory-intelligence/reorder-point-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_reorder-point-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

A3.8/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full behavioral burden and does a good job: it discloses the pricing model ($0.05 USDC), the payment failure mode (402 and no execution), the HTTP method/path, and the key side-effect boundary (does not create a purchase order). It omits output shape and how missing inputs like lead times are handled, which keeps it below a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences: formula first, then the non-side-effect clarification, then pricing, endpoint, and failure mode. Front-loaded with the highest-value information and free of filler.

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?

The pricing, payment failure, and endpoint are covered, which matters for a metered tool, and there is no output schema to explain. But with 16 optional parameters, nested objects, and no schema descriptions, an agent cannot determine what a valid minimal call looks like or how the four input-format parameters differ.

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, many of them nested and ambiguous (csv vs json vs text vs file, sales vs purchases, slowDays/slowUnits, serviceLevelZ). The description mentions 'history and lead times' and the formula references averageDailyDemand, leadTimeDays, reviewDays, and safetyStock, but it does not explain the alternative input formats or the optional parameters, leaving most of the surface undocumented.

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 and resource and even gives the exact formula being computed: reorderPoint = averageDailyDemand × (leadTimeDays + reviewDays) + safetyStock. It also distinguishes itself from write operations by saying 'No purchase order is created' and names the endpoint, so an agent can tell it apart from siblings like safety-stock-calculate.

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?

The description carves out a clear negative boundary (no PO created) and states the payment requirement, which implies this is a paid calculation-only endpoint. However, it never says when to prefer this over sibling calculators such as safety-stock-calculate or stockout-risk-calculate, nor what inputs are minimally required.

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