Skip to main content
Glama

Loyalty Redemption Cost

bpj_loyalty_redemption_cost
Read-onlyIdempotent

Estimate future fulfillment spend on outstanding loyalty points using a redemption assumption and cost per point.

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": {
      "points": "<points>",
      "redemption": "<redemption>",
      "perPoint": "<perPoint>"
    },
    "name": "bpj_loyalty_redemption_cost"
  }
}

Input Schema

NameRequiredDescriptionDefault
pointsYes
perPointYes
redemptionYes

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 readOnlyHint, idempotentHint, destructiveHint=false and a closed-world scope, so the safety profile is covered structurally. The description adds that this is a forward-looking estimate driven by an assumption, which is genuinely useful framing, but says nothing about the output shape, rounding, or that the result is unrounded spend in a single currency.

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 front-loaded sentence with no filler; the calculation inputs are stated in the order the agent needs them and nothing is repeated from the schema titles.

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 low-complexity, three-number read-only calculator whose safety profile is fully covered by annotations and which has no output schema, the description is close to sufficient. The remaining gap is that the estimation formula and units are not spelled out, which matters more for a calculator than for a lookup tool.

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 the parameter burden, and it does map all three inputs in plain language (outstanding points, redemption assumption, cost per point). However it never states the relationship between them (that spend is roughly points x redemption%/100 x perPoint), nor the currency or whether the redemption figure is a percentage rather than a fraction, leaving real ambiguity in a pure calculation tool.

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 verb ('Estimate') and a specific resource ('future fulfillment spend on outstanding loyalty points'), which is enough for an agent to distinguish it from generic cost tools. It does not explicitly contrast with the nearest sibling, bpj_gift_card_redemption_forecast, but the scope (points, not gift cards) is clear from the wording.

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 agent must infer that this is the right tool whenever outstanding point liability spend needs estimating, which is a reasonable inference but is not stated.

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.