Skip to main content
Glama

Stockout Opportunity Cost

bpj_stockout_opportunity_cost
Read-onlyIdempotent

Estimate stockout demand and forgone contribution, assuming customers switching to an in-house substitute retain equivalent contribution.

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": {
      "daily": "<daily>",
      "outDays": "<outDays>",
      "substitute": "<substitute>",
      "margin": "<margin>"
    },
    "name": "bpj_stockout_opportunity_cost"
  }
}

Input Schema

NameRequiredDescriptionDefault
dailyYes
marginYes
outDaysYes
substituteYes

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, idempotentHint, non-destructive and closed-world, so safety is covered. The description adds genuine modeling context with the assumption that customers switching to an in-house substitute retain equivalent contribution, which affects how the result should be interpreted. It stops short of stating the computation itself, the unit handling, or what the returned figure represents.

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 tightly written sentence with the core assumption front-loaded and no filler. It is efficient, though the brevity is partly under-specification rather than pure concision.

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 four-required-parameter quantitative model with no output schema, an agent needs the formula structure (demand times out-days times non-substituted share times margin) and the meaning/units of the returned value. Neither is provided, so the definition is thin relative to the tool's complexity.

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% and all four parameters are required, so the description carries the burden. It only clarifies the semantics of 'substitute' (share switching, contribution preserved) and implies 'margin' is per forgone unit, leaving 'daily' and 'outDays' interaction and the percentage-vs-fraction convention of 'substitute' unaddressed.

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 ('Estimate') and precise resources ('stockout demand and forgone contribution'), which lets an agent distinguish this from siblings such as bpj_inventory_carrying_cost. No explicit sibling contrast is offered, but the calculation is unambiguous.

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 use this versus related cost calculators, no prerequisites, and no exclusions (e.g., whether substitute share is a percentage or a fraction). The agent must infer that this is the right tool for stockout scenarios purely from the name and noun phrases.

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.