Skip to main content
Glama

Periodic Review Order-Up-To

bpj_periodic_review_order_up_to
Read-onlyIdempotent

Cover demand through both lead time and review interval, then deduct on-hand and inbound stock net of backorders.

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": {
      "daily": "<daily>",
      "lead": "<lead>",
      "review": "<review>",
      "buffer": "<buffer>",
      "stock": "<stock>",
      "pipeline": "<pipeline>",
      "back": "<back>"
    },
    "name": "bpj_periodic_review_order_up_to"
  }
}

Input Schema

NameRequiredDescriptionDefault
backYes
leadYes
dailyYes
stockYes
bufferYes
reviewYes
pipelineYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds the computational logic, which is useful, but says nothing about the sign or clamping of the result (e.g. whether a negative deficit floors at zero) or rounding of the days-based inputs.

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 compact sentence with no filler, and the demand-coverage step is front-loaded before the deduction step, mirroring the computation order. It could not be much shorter without losing the formula.

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?

This is a seven-required-parameter calculator with no output schema, so the description must explain what comes back; it never states that the result is an order quantity, its unit, or how a negative or zero result should be interpreted. That gap is significant for an agent that must act on the returned number.

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 reported as 0% in description text, but every parameter carries a descriptive title, and the prose ties the main inputs together: lead time and review interval are summed, on-hand plus inbound minus backorders is deducted. Only 'daily' and 'buffer' are not named explicitly, and their role is still clear from the formula.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The sentence describes the underlying algorithm (cover lead time plus review interval, subtract on-hand and inbound net of backorders) rather than stating a verb+resource such as 'Compute the periodic-review order-up-to quantity.' The resource name appears only in the title, and no sibling (e.g. bpj_inventory_order_quantity) is named, so the agent must infer the purpose from the formula.

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 guidance, no exclusions, and no pointer to alternative replenishment calculations among the many inventory siblings. The agent can only infer applicability from the formula itself.

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.