Skip to main content
Glama

Capped Threshold Coupon

bpj_capped_threshold_coupon
Read-onlyIdempotent

Check the merchandise threshold before applying the percentage coupon and cap the discount at the allowed amount.

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>",
      "discount": "<discount>",
      "cap": "<cap>"
    },
    "name": "bpj_capped_threshold_coupon"
  }
}

Input Schema

NameRequiredDescriptionDefault
capYes
discountYes
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?

The annotations already establish that this is a read-only, idempotent, non-destructive, closed-world calculation. The description adds the computation order (threshold check, percentage application, cap) but does not disclose edge-case behavior such as what happens when the subtotal is below the threshold.

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?

The definition is a single front-loaded sentence with no wasted wording. It communicates the core calculation 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 four-parameter calculation tool with no output schema, the description should clarify return semantics and edge cases. It explains the main algorithm but leaves open what is returned and how ineligible subtotals are handled; annotations cover safety but not these result details.

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 compensate. It maps the roles of threshold, percentage coupon, and cap, and implies subtotal via 'merchandise threshold', but it does not clarify units, ranges, or the exact meaning of each parameter beyond what the schema titles already convey.

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 operation: checking a merchandise threshold, applying a percentage coupon, and capping the discount. This clearly identifies it as a coupon-calculation tool and distinguishes it from unrelated sibling tools, though it does not explicitly name an 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?

It gives procedural steps for the calculation but no explicit guidance on when to choose this tool versus alternatives. There is no when-not-to-use guidance or mention of sibling tools.

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.