Skip to main content
Glama

Buy and Get Promotion Basket

bpj_buy_get_promotion_basket
Read-onlyIdempotent

Apply a same-price buy-X-get-Y-free promotion to complete groups, charging remaining ungrouped units at list price.

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>",
      "quantity": "<quantity>",
      "buy": "<buy>",
      "gift": "<gift>"
    },
    "name": "bpj_buy_get_promotion_basket"
  }
}

Input Schema

NameRequiredDescriptionDefault
buyYes
giftYes
priceYes
quantityYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare this as a read-only, idempotent, closed-world, non-destructive operation, so safety needs no restating. Beyond that, the description adds real behavioral substance: only complete groups receive the free units, and leftover ungrouped units are charged at list price. It does not say what the call returns or how rounding/partial groups are reported, which keeps it from a 5.

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?

One front-loaded sentence with no filler; the primary action comes first and the remainder-handling rule follows. The wording 'complete groups' is slightly dense and requires the reader to decode it, but nothing is wasted.

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, all-required calculation with no output schema, the description explains the pricing rule but not the result shape or edge cases (zero quantity, quantity below one group, exact multiples). An agent could invoke it correctly but would not know what to expect back.

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%, though the schema does carry titles ('Paid units required per promotion group', 'Free units per group', etc.) that describe each field. The description reinforces the mapping of buy/gift to the promotion and price to list price, but adds no constraints such as behavior when quantity is smaller than buy+gift or when buy exceeds quantity. It partially compensates for the coverage gap rather than fully closing it.

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 gives a specific verb and resource: applying a same-price buy-X-get-Y-free promotion to a basket. It is clearly distinguishable from the pricing/forecasting siblings around it. It stops short of naming any related tool for comparison, but the computational intent is unambiguous.

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, no prerequisites, and no named alternative. The phrase 'apply ... to complete groups' only implies the scenario; an agent must infer that this is the promotion-pricing path rather than a plain price lookup.

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.