Skip to main content
Glama

Business Calculator: GST, Margin & Everyday Formulas

Inventory, Purchase, Logistics & Production Calculators — Saifs AI

inventory_logistics_calculators
Read-only

Calculate stock, purchase, shipping and production numbers exactly: EOQ, reorder point, safety stock z·σ·√L, days of cover; inventory turnover, DIO, fill rate, FIFO and weighted-average stock valuation, dead stock %; landed cost (freight / duty / insurance allocated by value, weight or qty), import duty BCD + SWS + IGST; courier volumetric and chargeable weight, CBM, cartons, pallets; OEE, capacity utilisation, takt and cycle time, yield / scrap, Little's law. Returns a standard-library Python script with only these calculators (eoq_reorder_calculator, inventory_metrics_calculator, landed_cost_calculator, shipping_weight_calculator, production_efficiency_calculator) to run in your code sandbox; each answer gives result, formula, inputs used, rounding, rule version and effective date. Inputs: tools (narrow to some of these calculators), calls ([{tool, operation, inputs, rounding?, as_of?}] baked into the script; a calculator from another area named in calls is added), calls_path (JSON file of calls in your sandbox). Calculation never runs on this server or any API. Not for EMI / interest / NPV / IRR (refused), nor demand forecasting (MCP 18) or multi-SKU optimisation (MCP 16). Operation and input names: business_calculator_list_formulas.

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_logistics_calculators"
  }
}

Input Schema

NameRequiredDescriptionDefault
callsNoCalculations to bake into the script (their calculators are included).
toolsNoNarrow the script to some of this area's calculators (default: all of them).
calls_pathNoJSON file of calls already in your sandbox.
full_catalogNoKeep descriptions and worked examples inside the script (larger).

Output Schema

NameRequiredDescriptionDefault
areaNo
notesNo
scriptYes
languageNo
requiresNo
calls_pathNo
operationsNo
call_formatNo
instructionsYes
writes_filesNo
calls_baked_inNo
engine_versionYes
included_toolsYes
server_computesNo
network_access_requiredNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnlyHint/openWorldHint=false/destructiveHint=false, but the description adds genuinely non-obvious behavior: it returns a standard-library Python script to run in the caller's sandbox, 'Calculation never runs on this server or any API', and each answer carries result, formula, inputs used, rounding, rule version and effective date. It also discloses that a calculator from another area named in calls is silently added, and that the full_catalog flag inflates script size.

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?

Front-loads the domain and formula list, then moves to return artifact, then inputs, then exclusions — a sensible order with no filler sentences. The dense formula enumeration (EOQ, safety stock z·σ·√L, BCD + SWS + IGST, CBM, OEE, Little's law) is long but serves as selection signal rather than padding.

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

Completeness5/5

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

For a tool that emits an executable script with heterogeneous call payloads, the definition covers what is produced, where it runs, what each input does, rounding/date-versioning behavior, and the refusal boundary. With an output schema present it need not describe return values further, and nothing an agent needs to invoke it correctly appears to be missing.

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

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3; the description earns more by explaining the semantic consequence of each parameter — tools narrows the script, calls are 'baked into the script' and import their calculators, calls_path is a JSON file already in the sandbox. The detail that naming a foreign calculator in calls pulls that calculator in is meaning not present in the schema at all.

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?

States a specific verb and resource set ('Calculate stock, purchase, shipping and production numbers') and enumerates the exact calculators shipped (eoq_reorder_calculator, inventory_metrics_calculator, landed_cost_calculator, shipping_weight_calculator, production_efficiency_calculator). An agent can tell instantly this is the inventory/logistics/production calculation area and not the finance, GST, HR, or pricing sibling areas.

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?

Gives explicit when-not guidance with named alternatives: 'Not for EMI / interest / NPV / IRR (refused), nor demand forecasting (MCP 18) or multi-SKU optimisation (MCP 16)'. It also routes the agent to business_calculator_list_formulas for operation and input names. What it lacks is an explicit positive routing statement against the sibling areas (finance_mis_calculators, pricing_profit_calculators), leaving the boundary to be inferred from the calculator list.

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.