Skip to main content
Glama

Inventory Cost Rollforward

bpj_inventory_cost_rollforward
Read-onlyIdempotent

Reconcile opening inventory, net purchases and closing inventory to cost of goods sold.

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": {
      "opening": "<opening>",
      "purchases": "<purchases>",
      "closing": "<closing>"
    },
    "name": "bpj_inventory_cost_rollforward"
  }
}

Input Schema

NameRequiredDescriptionDefault
closingYes
openingYes
purchasesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior2/5

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

The annotations already establish read-only, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds little behavioral context beyond the purpose: it does not state the reconciliation formula, rounding/currency assumptions, validation behavior, or what value is returned.

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 front-loaded sentence with no filler. Every word contributes to the stated purpose.

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

Completeness3/5

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

For a simple three-parameter calculation tool, the definition gives the essential purpose and names all inputs. With no output schema, however, it should explicitly state what is returned (the reconciled COGS figure) and ideally the formula, so completeness is adequate but not full.

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%, so the description must carry parameter meaning. It names the three inputs and frames them as an inventory reconciliation, but it does not clarify the formula or treatment details (e.g., COGS = opening + purchases - closing) or unit/currency assumptions, leaving the parameters only partially explained beyond their titles.

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 states a specific verb ('Reconcile') and names the exact resource and inputs: opening inventory, net purchases, closing inventory, and cost of goods sold. It clearly distinguishes this from sibling inventory tools like carrying cost or reorder point, though it does not explicitly name an alternative.

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

Usage Guidelines3/5

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

Usage is implied by the accounting reconciliation purpose: an agent can infer this is for deriving COGS from inventory movements. However, there is no explicit guidance on when to use it versus alternatives, nor any stated prerequisites or exclusions.

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.