Skip to main content
Glama
tresor4k

macalc

calculate_inventory_eoq

Compute the Economic Order Quantity (EOQ) using the Wilson formula for supply chain optimization. Input annual demand, order cost, and holding cost per unit to obtain the optimal order quantity and number of orders per year.

Instructions

Compute Economic Order Quantity (Wilson formula). Use for supply chain optimization. Inputs: annual demand, order cost, holding cost per unit. Returns EOQ and orders/year. See list_bundles for related 'finance-universal' calculators.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
annual_demandYesAnnual demand units
order_costYesCost per order
holding_costYesAnnual holding cost per unit

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultNoComputed result. Object whose fields depend on the tool (e.g. {tax, marginal_rate, brackets} for tax tools, {volume_l, gallons} for volume tools).
formulaNoHuman-readable formula or method used (e.g. "I=P·r·t", "Magnus formula").
sourceNoAuthoritative source for the rule or formula (e.g. "Article 197 CGI", "NF DTU 21").
reference_urlNoLink to a calcul2 page documenting the calculation in detail.
Behavior3/5

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

No annotations provided, so description carries full burden. States it returns EOQ and orders/year, but omits whether it is read-only or has side effects. Minimal behavioral info.

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?

Three sentences front-loaded with purpose, then usage, then inputs/outputs. No wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers inputs, output, formula, and usage context. Output schema exists but description still mentions returns. Slightly missing explicit annual nature of holding cost, though schema covers it.

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 has 100% coverage and descriptions. Description restates parameter names without adding new meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states it computes Economic Order Quantity using the Wilson formula, with specific verb and resource. Distinguishes from sibling calculate_inventory_turnover implicitly.

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?

Explicitly says 'Use for supply chain optimization' and directs to related calculators via list_bundles. Does not mention when not to use or alternatives like calculate_inventory_turnover.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/tresor4k/macalc-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server