Skip to main content
Glama

Reorder point and inventory replenishment calculator

calculate_reorder_point
Read-only

Calculate a SKU's reorder point, stock coverage and indicative replenishment quantity using daily demand, lead time, safety stock and committed units. The model assumes constant demand and lead time. It does not optimize purchase minimums, case multiples, campaigns, expiry, financing or supplier variability. With zero demand, coverage days are undefined. Confirmed inbound can improve position without preventing a stockout before arrival: check its timing. Input fields: dailyDemand: Your projection, excluding orders already counted as reserved. leadDays: From purchase placement to usable stock. reviewDays: Additional horizon used to calculate the replenishment target. safetyUnits: Your chosen buffer; no statistical service level is inferred. onHandUnits: Include your safety buffer; exclude damaged or unusable goods. reservedUnits: Unshipped commitments. They may exceed physical stock. incomingUnits: Only units usable within the lead time. A delay changes the scenario.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "dailyDemand": "<dailyDemand>",
      "leadDays": "<leadDays>",
      "reviewDays": "<reviewDays>",
      "safetyUnits": "<safetyUnits>",
      "onHandUnits": "<onHandUnits>",
      "reservedUnits": "<reservedUnits>",
      "incomingUnits": "<incomingUnits>"
    },
    "name": "calculate_reorder_point"
  }
}

Input Schema

NameRequiredDescriptionDefault
leadDaysYes
reviewDaysYes
dailyDemandYes
onHandUnitsYes
safetyUnitsYes
incomingUnitsYes
reservedUnitsYes

Output Schema

NameRequiredDescriptionDefault
toolYes
methodYes
statusYes
metricsYes
sourcesYes
currencyNo
limitationsYes
vatIncludedNo
pendingFieldsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare a read-only, closed-world, non-destructive operation, so the description is not needed for safety. It still adds substantive behavior beyond that: modeling assumptions, the zero-demand edge case where coverage days become undefined, and the warning that confirmed inbound can improve position without preventing a stockout before arrival. These are non-obvious traits an agent could not infer from annotations or schema.

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, then assumptions, then caveats, then the field glossary — a sensible order with no filler sentences. It is dense and the caveat clauses stack up somewhat, but each one carries distinct information.

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?

For a seven-parameter calculation tool with an output schema already present, the description supplies everything needed: purpose, assumptions, edge cases, and per-field definitions. Return values need not be explained because the output schema exists.

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

Parameters5/5

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

Schema description coverage is 0%, so the description carries the full burden, and it documents all seven required parameters with meaning rather than type: dailyDemand excludes reserved orders, leadDays runs to usable stock, safetyUnits implies no statistical service level, onHandUnits includes buffer but excludes damaged goods, reservedUnits may exceed physical stock. The only minor gap is that reviewDays is explained in terms of the replenishment target rather than a concrete formula.

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?

The opening sentence names a specific verb ('Calculate') and three concrete outputs (reorder point, stock coverage, indicative replenishment quantity) plus the input basis. An agent knows exactly what this tool produces without reading the schema.

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?

The description explicitly scopes the model ('assumes constant demand and lead time') and lists what it does not handle (purchase minimums, case multiples, campaigns, expiry, financing, supplier variability), which tells the agent when to look elsewhere. It lacks a positive 'use this when' statement for a specific scenario, but with no siblings present the exclusions carry most of the routing value.

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