Skip to main content
Glama

FIFO Lot Issue

bpj_fifo_lot_issue
Read-onlyIdempotent

Consume the older lot first and show the quantity issued from each lot and the remaining inventory cost.

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": {
      "first": "<first>",
      "firstCost": "<firstCost>",
      "second": "<second>",
      "secondCost": "<secondCost>",
      "issue": "<issue>"
    },
    "name": "bpj_fifo_lot_issue"
  }
}

Input Schema

NameRequiredDescriptionDefault
firstYes
issueYes
secondYes
firstCostYes
secondCostYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered and the description correctly implies a pure calculation. It adds useful disclosure about what is returned (per-lot issued quantities and remaining inventory cost), but is silent on edge behavior such as what happens when the issue quantity exceeds the combined lot units.

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 sentence with zero waste: the allocation rule comes first and the return values follow. Nothing is padded and nothing needs reordering.

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

Completeness2/5

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

With five required, undocumented parameters, no output schema, and no stated handling of degenerate cases (issue larger than both lots, zero quantities, cost ordering assumptions), the description leaves too much for an agent to guess. It should at least state the units and the over-issue behavior for a tool this parameter-heavy.

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% — the five required parameters carry only titles like "Older lot units" and "Issue quantity". The description gestures at the concept of two lots and an issue quantity but never maps inputs to parameters, states units, or explains how costs are used in the remaining-cost figure, so it fails to compensate for the coverage gap.

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?

The description names a specific verb and method ("consume the older lot first") plus the output it produces (quantity issued per lot and remaining inventory cost), which is far more than a restatement of the name. It implicitly distinguishes FIFO from the weighted-average sibling via the explicit older-lot-first rule, but never names that alternative, so an agent must infer the contrast.

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 when-to-use or when-not guidance and no reference to the obvious alternative method (bpj_weighted_average_stock_issue). The FIFO rule is stated as mechanics, not as a selection criterion, so the agent gets no help choosing between costing methods.

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.