Skip to main content
Glama

BRAINIAC Inventory Intelligence

Calculate safety stock

inventory-intelligence_safety-stock-calculate

Calculate safetyStock = serviceLevelZ × demandStdev × sqrt(leadTimeDays). Short history raises disclosed uncertainty. Seasonality is not invented. Price $0.05 USDC. POST /api/v1/inventory-intelligence/safety-stock-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_safety-stock-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

C2.9/5.0
Behavior3/5

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

With no annotations supplied, the description must carry the full behavioral burden, and it does add real value: it discloses the pricing ($0.05 USDC), the POST endpoint, the 402 failure mode for unpaid calls, and that uncertainty is surfaced rather than inferred when history is short. It still omits whether the call is read-only/side-effect-free, how conflicts among the parallel input formats are resolved, and what the response contains.

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?

The formula and the two caveats are front-loaded, and each subsequent sentence (pricing, endpoint, 402 behavior) carries operational weight for an agent deciding whether to call. Slightly dense run-on phrasing around 'Short history raises disclosed uncertainty. Seasonality is not invented.' costs it the top score.

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?

For a 16-parameter tool with nested objects, no annotations, no output schema, and 0% schema coverage, the description leaves far too much unexplained — particularly input-source precedence and expected output. It is strong on the formula and cost behavior but inadequate for correct invocation.

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, and the description only touches serviceLevelZ and leadTimeDays (the latter nested inside suppliers); demandStdev is not even a parameter, it is derived. Nothing explains sales, products, purchases, suppliers, asOf, historyDays, forecastDays, reviewDays, slowDays, slowUnits, excessDaysCover, or the csv/json/text/file alternatives, so the gap is substantial.

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 verb and resource and even gives the exact formula (serviceLevelZ × demandStdev × sqrt(leadTimeDays)), which makes clear this is a statistical safety-stock computation rather than a reorder-point or stockout-risk calculation. It does not explicitly name a sibling to contrast against, so it falls just short of 5.

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 statement of when to choose this tool over reorder-point-calculate or stockout-risk-calculate, and no guidance on which of the many input paths (sales array vs. csv vs. json vs. file) should be used. The caveats about short history and seasonality hint at applicable conditions but do not constitute usage guidance.

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