Skip to main content
Glama

Inventory Reorder Point

bpj_inventory_reorder_point
Read-onlyIdempotent

Compare inventory position with expected lead-time demand and safety stock to flag a reorder.

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>",
      "leadTime": "<leadTime>",
      "safetyStock": "<safetyStock>",
      "inStock": "<inStock>",
      "onOrder": "<onOrder>",
      "backorder": "<backorder>"
    },
    "name": "bpj_inventory_reorder_point"
  }
}

Input Schema

NameRequiredDescriptionDefault
inStockYes
onOrderYes
leadTimeYes
backorderYes
dailyDemandYes
safetyStockYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered and the description correctly does not contradict it. What the description adds is the decision logic domain (lead-time demand versus safety stock), which is useful. What it omits is the form of the result: whether 'flag a reorder' yields a boolean, a threshold value, or a recommended action, and there is no output schema to fill that gap.

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 no filler, and the operative concept (compare position to demand and safety stock) leads. It is arguably over-compressed for a six-parameter calculation, but nothing is wasted.

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?

This is a pure computation tool with six required parameters and no output schema, so the description is the only place the agent can learn what comes back. It never explains the return value, the formula tying the inputs together, or how ties/edge cases (zero lead time, backorders exceeding stock) are handled. For a tool of this shape, that leaves a real decision-relevant gap.

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%, so the description must carry the burden, but it only gestures at parameter groupings ('inventory position', 'expected lead-time demand', 'safety stock') without saying which parameters compose them. Critically, it never states that inventory position is on-hand plus on-order minus backorder, leaving the sign convention of the backorder parameter ambiguous. The field titles help somewhat, but the actual formula — the main thing an agent needs to trust the inputs — is unstated.

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 computation: comparing inventory position against lead-time demand plus safety stock to flag a reorder. That is a clear verb-plus-resource statement an agent can act on. It stops short of distinguishing itself from the sibling bpj_inventory_order_quantity, which sounds adjacent (computing how much to order rather than whether to reorder).

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 explicit when-to-use or when-not-to-use guidance, and no named alternative. The closest thing is the implicit trigger 'flag a reorder', which tells the agent the decision context but not how to choose this over bpj_inventory_order_quantity or other inventory tools.

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.