Skip to main content
Glama

Discount and Cashback Net Spend

bpj_discount_cashback_net_spend
Read-onlyIdempotent

Discount the list price first, then accrue cashback on the actual payment to distinguish checkout payment from eventual net spend.

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>",
      "cashback": "<cashback>"
    },
    "name": "bpj_discount_cashback_net_spend"
  }
}

Input Schema

NameRequiredDescriptionDefault
priceYes
cashbackYes
discountYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world, non-destructive, so the safety profile is fully covered. The description does add real behavioral value by fixing the operation order (discount before cashback) and clarifying that cashback accrues on the amount actually paid, not the list price. It stops short of stating what the tool returns or how rounding is handled.

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 tight sentence with the ordering constraint front-loaded and no filler. It could be slightly clearer by naming the computed outputs, but nothing is wasted.

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 calculation tool with no output schema, so the description is the only place an agent can learn what comes back — yet it never says whether the result is net spend alone, or both checkout payment and net spend. For a three-required-parameter formula with zero schema description coverage, that is a meaningful gap.

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 partially does by establishing the sequence between 'price', 'discount', and 'cashback' and clarifying cashback applies to the post-discount payment. It does not confirm units (percent vs amount) beyond what the schema titles imply, nor whether all three inputs are required together.

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 — apply the first percentage discount to list price, then accrue cashback on the discounted payment — and frames the goal as separating checkout payment from eventual net spend. That is concrete enough to distinguish it from sibling discount/cost tools, though the tool name itself carries most of the identification.

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 guidance on when to reach for this tool versus siblings like bpj_annual_plan_discount or bpj_trade_credit_discount_cost, and no exclusions or prerequisites. The ordering statement ('discount first, then cashback') hints at the scenario but never states the use case explicitly.

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.