Skip to main content
Glama

Economic Order Quantity

bpj_inventory_order_quantity
Read-onlyIdempotent

Estimate the economic order quantity for steady demand, fixed order cost, and no quantity discounts.

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": {
      "annualDemand": "<annualDemand>",
      "orderCost": "<orderCost>",
      "holdingCost": "<holdingCost>"
    },
    "name": "bpj_inventory_order_quantity"
  }
}

Input Schema

NameRequiredDescriptionDefault
orderCostYes
holdingCostYes
annualDemandYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare this a safe, read-only, idempotent, closed-world computation, so the bar is lower. The description usefully adds the model's simplifying assumptions, but says nothing about the returned quantity (units, rounding, whether a cost breakdown comes back) for a tool with no output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler; the verb and resource come first and the qualifiers follow. Every clause carries information.

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?

For a three-parameter calculator with no output schema, the definition covers what the tool models but omits what the agent gets back and any caveat about the formula's limits. Adequate to trigger a correct call, not sufficient to interpret the result confidently.

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% – only bare titles exist – so the description is expected to compensate for the three required inputs. It names demand, order cost, and holding cost in prose, but adds no units, periodicity (the schema says annual holding cost, the description only says 'holding cost'), or acceptable ranges beyond what the schema enforces.

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?

Names a specific operation ("Estimate the economic order quantity") plus the modeling regime it applies to, which is enough to tell it apart from cost/stock siblings such as reorder-point or break-even calculators. It stops short of naming any sibling explicitly, so it sits at a clear-but-undifferentiated 4.

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 three stated preconditions (steady demand, fixed order cost, no quantity discounts) function as real applicability gates an agent can check before calling, which is stronger than implied usage. There is no explicit 'when not to use' alternative or fallback for non-steady demand or discount schedules, so it is not a 5.

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.