Skip to main content
Glama

Exchange Offer Increment

bpj_exchange_offer_increment
Read-onlyIdempotent

Compare offering a replacement with refunding now; a kept exchange retains the sale and every attempt consumes a replacement and shipping.

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>",
      "cost": "<cost>",
      "retain": "<retain>",
      "replacement": "<replacement>"
    },
    "name": "bpj_exchange_offer_increment"
  }
}

Input Schema

NameRequiredDescriptionDefault
costYes
priceYes
retainYes
replacementYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered and this tool is clearly a pure calculator. The description adds genuine modeling context beyond the annotations: that a kept exchange retains the sale and that each attempt consumes both a replacement and shipping cost. What remains undisclosed is the calculation itself – the formula, output units, and how the retain percentage weights the outcome.

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 compact sentence with no filler, front-loading the comparison and following with the two economic assumptions. It is dense but every clause carries information; a small structural improvement would be to state the computed result explicitly first.

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?

Placeholder check: the tool takes four required numeric parameters, has no output schema, and zero schema description coverage, so the description should convey what value is returned and in what units. It conveys the modeling logic but not the output, leaving an agent unable to predict the result format.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%; only the property titles ('Listed unit price', 'Merchandise unit cost', 'Share of replacement orders kept (%)', 'Extra cost of shipping a replacement') carry meaning. The description gestures at two of the four parameters ('kept exchange' → retain, 'consumes a replacement and shipping' → replacement) but says nothing about price or cost or how units/percentages combine, so it does not compensate for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description frames the tool as a comparison between offering a replacement and refunding now, and adds domain framing ('a kept exchange retains the sale'), which hints at an incremental-value calculation. However, it never states the concrete operation or output ('calculate the incremental profit/expected value of offering X% of replacements'), so an agent must infer the result shape. No sibling tool is named or differentiated, even though siblings like bpj_retention_offer_lift_value are close analogues.

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 pointer to an alternative tool for a related calculation. The phrase 'Compare offering a replacement with refunding now' implies the scenario loosely but does not tell an agent which situations call for this tool versus the other offer/retention calculators.

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.