Skip to main content
Glama

Minimum Cart Upsell Quantity

bpj_minimum_cart_upsell_gap
Read-onlyIdempotent

Find the smallest number of whole add-on items required to cross a basket threshold and quantify the overshoot.

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": {
      "subtotal": "<subtotal>",
      "threshold": "<threshold>",
      "price": "<price>"
    },
    "name": "bpj_minimum_cart_upsell_gap"
  }
}

Input Schema

NameRequiredDescriptionDefault
priceYes
subtotalYes
thresholdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world scope, so safety and repeatability need no restatement. The description adds that the result quantifies overshoot in addition to the item count, which is genuine output context. It does not say whether crossing the threshold is strict or inclusive, nor what the returned values look like.

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; both the primary quantity (item count) and the secondary quantity (overshoot) are stated efficiently.

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 three-parameter arithmetic tool with a closed-world read-only profile, the description covers the core intent but omits the behavioral detail that matters most: what happens when subtotal already meets the threshold, and that the output is a count plus an amount. With no output schema, that return-value description would have been worth including.

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 parameter meaning, and it does partially: add-on items imply a per-unit price, basket threshold implies the target subtotal, and the smallest whole count implies integer rounding up. However, it never binds these to the three named parameters or clarifies whether price is tax-inclusive, currency units, or whether the threshold comparison is >= or >.

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 computation: the minimum count of whole add-on units needed to reach a basket threshold, plus the overshoot amount. That is a clear verb+resource for a pure calculation tool and is distinguishable from generic gap-filling siblings by its cart/threshold framing. It stops short of contrasting itself with any named 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 or when-not-to-use guidance, and no mention of the obvious boundary case (subtotal already at or above threshold). Usage is only inferable from the stated goal, so the agent must guess the intended scope and edge-case behavior.

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.