Skip to main content
Glama

Purchase Case Rounding

bpj_purchase_case_rounding
Read-onlyIdempotent

Raise positive net demand to the supplier minimum and then round to a whole case, reporting excess units.

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": {
      "demand": "<demand>",
      "minimum": "<minimum>",
      "pack": "<pack>"
    },
    "name": "bpj_purchase_case_rounding"
  }
}

Input Schema

NameRequiredDescriptionDefault
packYes
demandYes
minimumYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/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 still adds real behavioral value by spelling out the ordering of the two operations and that an excess-units figure is produced, which is the key thing an agent needs to know about a pure calculation.

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 that states the algorithm in execution order and ends with the reported output. No filler, no repetition of schema or annotation facts.

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?

There is no output schema, and the description compensates by noting the reported excess units, though it never says what the primary return value is (presumably the rounded case quantity). For a three-integer pure function with full annotation coverage, this is nearly sufficient, with only minor edge-case gaps.

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 0%, so the description must carry the parameter meaning. It does map loosely onto the three inputs ('net demand', 'supplier minimum', 'whole case'), but the mapping stays informal and never names which value is the case size or clarifies the interaction when minimum is zero or below demand.

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 concrete two-step operation (raise to supplier minimum, then round to a whole case) plus a side effect (reporting excess units), which is far more specific than the name alone. It does not explicitly contrast itself with nearby siblings such as packout-related tools, so it stops short of a 5.

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 only implied: 'positive net demand' hints that zero demand is not raised, but there is no explicit when-to-use, when-not-to-use, or named alternative. The agent can infer this is a purchasing-quantity normalization step, but must supply the context 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.