Skip to main content
Glama

Gift Card Redemption Forecast

bpj_gift_card_redemption_forecast
Read-onlyIdempotent

Reconcile gift card face value with actual redemptions and an expected lifetime non-redemption share to project further redemptions.

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": {
      "issued": "<issued>",
      "redeemed": "<redeemed>",
      "breakage": "<breakage>"
    },
    "name": "bpj_gift_card_redemption_forecast"
  }
}

Input Schema

NameRequiredDescriptionDefault
issuedYes
breakageYes
redeemedYes

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 cover read-only, idempotent, closed-world, and non-destructive behavior, so the description's added value is the forecast basis. It discloses that the projection uses actual redemptions plus expected lifetime breakage, but not assumptions, time horizon, precision, or output shape.

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?

Single sentence with no filler, front-loading the verb and ending with the forecast outcome. It is dense but readable and appropriately sized for a three-parameter calculator.

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 simple read-only calculator, the definition covers purpose and inputs, and annotations cover safety. However, with no output schema, it does not state what the forecast returns (amount, schedule, etc.) or key projection assumptions, leaving gaps an agent may need.

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

Parameters4/5

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

With 0% schema description coverage, the description carries the burden; it maps all three parameters to roles (issued as face value, redeemed as actual redemptions, breakage as expected non-redemption share) and explains how they combine. It does not add format or unit details beyond the schema titles, so it is helpful but not exhaustive.

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 uses a specific verb ('Reconcile ... to project') and resource ('gift card face value' and 'redemptions'), making the operation identifiable. It does not explicitly differentiate this forecast from sibling calculators such as loyalty redemption cost, so it stops short of a 5.

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, when-not-to-use, prerequisite, or alternative-tool guidance. The phrase 'to project further redemptions' hints at the forecasting use case, but selection among sibling forecast tools is left to inference.

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.