Skip to main content
Glama

efficiency

calculate_inventory_turnover

Read-onlyIdempotent

Calculate inventory turnover: cost of goods sold divided by average inventory — how many times inventory is sold and replaced in a period. Formula: Inventory Turnover = COGS / Average Inventory. WHEN TO USE: Use to assess inventory management and demand strength; rising turnover usually means better stock discipline or strong demand. WHEN NOT TO USE: Do NOT use COGS-based turnover for service businesses with negligible inventory, and always pair with days inventory outstanding for intuition. BEHAVIOUR: pure deterministic calculation — no side effects, no network or storage access; idempotent and non-destructive; identical inputs always produce identical outputs. Division by zero or non-finite inputs returns an explicit error instead of a number. RETURNS: JSON object { inventory_turnover: number (e.g. 6.0 = 6.0x per year), inputs }. PARAMETERS: cogs (required): Cost of goods sold for the period, e.g. 600000. Must be >= 0. begin_inventory (required): Inventory at period start, e.g. 90000. Must be >= 0. end_inventory (required): Inventory at period end, e.g. 110000. Must be >= 0.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cogsYesCost of goods sold for the period, e.g. 600000. Must be >= 0.
end_inventoryYesInventory at period end, e.g. 110000. Must be >= 0.
begin_inventoryYesInventory at period start, e.g. 90000. Must be >= 0.

TDQS

A4.8/5.0
Behavior5/5

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

Description goes well beyond the annotations by stating it is a pure deterministic calculation with no side effects, no network or storage access, idempotence, and identical outputs for identical inputs. It also discloses error behavior for division by zero or non-finite inputs. This fully matches the readOnlyHint and idempotentHint annotations.

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 description is well-structured with labeled sections (WHEN TO USE, BEHAVIOUR, RETURNS, PARAMETERS) and front-loads the definition and formula. It is slightly repetitive because the PARAMETERS section duplicates the schema descriptions, which are already present and complete, preventing a perfect score.

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?

There is no output schema, so the RETURNS section rightly provides the JSON shape and an example. The description covers the formula, common use, exclusion, error handling, and all parameters. Nothing critical is missing for an agent to invoke this deterministic calculator correctly.

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 coverage is 100%, so the baseline is 3. The description adds semantic value by presenting the formula, which clarifies that begin_inventory and end_inventory are combined into an average, and by showing an example output. The parameter list largely repeats the schema, but the formula provides the extra relationship.

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?

Description opens with a specific verb and resource: 'Calculate inventory turnover' plus the formula COGS / Average Inventory and the meaning 'how many times inventory is sold and replaced in a period.' This unambiguously distinguishes it from sibling tools such as calculate_asset_turnover or calculate_days_inventory_outstanding.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The 'WHEN TO USE' section states the intended business assessment, and 'WHEN NOT TO USE' warns against service businesses and instructs pairing with days inventory outstanding. It explicitly names a sibling metric as a complement, giving the agent clear routing 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.

TDQS

A4.4/5.0
Disambiguation4/5

Each tool calculates a distinct financial efficiency ratio, but some boundaries are close: the turnover/day pairs (e.g., inventory_turnover vs. days_inventory_outstanding) cover conceptually related metrics, and asset_turnover vs. fixed_asset_turnover could initially be confused. The detailed WHEN TO USE guidance does help disambiguate, so misselection risk is low but not zero.

Naming Consistency5/5

All tool names follow the exact same calculate_<metric> pattern, making the set highly predictable and easy to scan. There are no mixed conventions, position variations, or inconsistent verb forms.

Tool Count5/5

Nine tools is a well-scoped size for a financial efficiency calculation server. Each tool corresponds to a standard, distinct efficiency ratio, and none feel redundant or unnecessary.

Completeness4/5

The set covers the core efficiency ratio family comprehensively: asset, fixed asset, inventory, receivable, and payable turnover, plus their days-based counterparts and the cash conversion cycle. Minor gaps remain, such as no direct working-capital-turnover or operating-cycle calculator, but agents can assemble those from the existing outputs.

Resources