Skip to main content
Glama

Fixed Lead-Time Safety Stock

bpj_fixed_lead_safety_stock
Read-onlyIdempotent

Estimate safety stock for independent daily demand and constant lead time using the supplied normal service quantile.

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": {
      "deviation": "<deviation>",
      "lead": "<lead>",
      "z": "<z>"
    },
    "name": "bpj_fixed_lead_safety_stock"
  }
}

Input Schema

NameRequiredDescriptionDefault
zYes
leadYes
deviationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile needs no restating. The description adds the modeling preconditions (constant lead time, independent demand) but omits the actual computation form and the output units, which are the behaviors that matter for a math tool.

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 well-formed sentence with the assumptions front-loaded and no filler. It could have spent one more clause on the formula or output units without becoming bloated.

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?

With no output schema, the description should say what value comes back and in what units, which it does not. For a three-parameter formula tool the definition is adequate but leaves the agent guessing at the exact expression being evaluated.

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

Parameters3/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 load; it does gesture at all three inputs (normal service quantile, lead time, demand deviation). However, it never states how lead time enters the calculation (square-root-of-lead scaling) or the units of the result, leaving key parameter semantics to the schema titles.

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 ("Estimate safety stock") and pins the modeling assumptions (independent daily demand, constant lead time). It is clearly distinguishable from the unrelated sibling calculators, though it does not explicitly contrast with a variable-lead-time counterpart.

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 assumptions "independent daily demand and constant lead time" implicitly tell the agent when the model applies and when it does not, but there is no explicit when-to-use statement, prerequisite, or named alternative. Usage must be inferred from the stated conditions.

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.