Skip to main content
Glama

Sequential Retail Discounts

bpj_sequential_retail_discounts
Read-onlyIdempotent

Apply two discounts sequentially to the remaining merchandise price and show the effective combined saving.

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": {
      "price": "<price>",
      "discount": "<discount>",
      "second": "<second>"
    },
    "name": "bpj_sequential_retail_discounts"
  }
}

Input Schema

NameRequiredDescriptionDefault
priceYes
secondYes
discountYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare this as a pure, idempotent, non-destructive read-style calculation, so the burden is low. The description adds genuinely useful behavior beyond them by stating the discounts are applied sequentially to the remaining price and that a combined saving is surfaced. It does not disclose rounding/precision, currency assumptions, or 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 sentence with no filler, and the operation plus its key semantic constraint (sequential application to the remaining price) is front-loaded. Nothing in it could be removed without losing meaning.

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?

For a three-numeric-parameter calculation with a full annotation set and no output schema, the description covers the operation, the base amount, and the output intent ('effective combined saving'). The remaining gaps are precision/rounding and exact return shape, which are minor for a deterministic arithmetic helper.

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%, but the schema titles carry real meaning ('Listed unit price', 'First percentage discount (%)', 'Second percentage discount (%)'). The description reinforces that both values are percentages applied in order and that the first reduces the price before the second applies, but it does not state how 'discount' vs 'second' map to first/second, nor any rounding behavior.

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 uses a specific verb ('apply') with a specific resource ('two discounts sequentially') and clarifies the base is the 'remaining merchandise price', not the original list price. This distinguishes compounding from additive discounting, which is the key ambiguity. It does not name or differentiate itself from any sibling, though most listed siblings are unrelated calculators.

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 alternative is named. The phrase 'sequential' implies the use case (stacked percentage discounts), but an agent must infer that this is for chained percentage reductions rather than flat-amount markdowns or tax-adjusted pricing.

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.