Skip to main content
Glama

Inventory Carrying Cost

bpj_inventory_carrying_cost
Read-onlyIdempotent

Apply a combined annual carrying rate to average inventory cost for the stated fraction of a year.

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": {
      "average": "<average>",
      "carry": "<carry>",
      "period": "<period>"
    },
    "name": "bpj_inventory_carrying_cost"
  }
}

Input Schema

NameRequiredDescriptionDefault
carryYes
periodYes
averageYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds that this is a prorated cost computation, but it does not state the formula (whether it is carry% divided by 100 times average times period/12), whether compounding applies, or what the returned value represents. For a pure computation tool these omissions matter more than they would for a simple read.

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 well-formed sentence with no filler, and the core operation is front-loaded. It is slightly over-compressed: the brevity comes at the cost of the unit and output clarifications noted above.

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?

For a three-parameter, side-effect-free calculator with annotations covering behavior and no output schema, the description covers the what and the rough how. The main remaining gap is the meaning and units of the returned cost figure, which nothing else in the definition supplies.

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 description coverage is reported at 0 percent, though each parameter carries an informative title (rate in percent, period in months, average at cost). The description reinforces that the rate is annual and the base is at cost, and it links period to a fraction of a year, but it never states the unit of 'period' as months nor how the three inputs combine into a result.

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 action applied to a specific resource: applying a combined annual carrying rate to average inventory cost over a fraction of a year. An agent can tell this is a rate-times-base cost calculation, distinct from rollforward or reorder-point siblings. It does not, however, name or contrast a sibling alternative.

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 explicit when-to-use, when-not-to-use, or alternative-tool guidance. The phrase 'for the stated fraction of a year' implies partial-period proration is supported, but nothing tells the agent when this calculation is the right choice versus a rollforward or a stockout-cost tool.

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.