Skip to main content
Glama

redeem_loyalty_reward

DestructiveIdempotent

Record a reward redemption for the specified member and programme revision. Reuse the redemption ID on retry.

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": {
      "id": "<id>",
      "memberId": "<memberId>",
      "programRevision": "<programRevision>"
    },
    "name": "redeem_loyalty_reward"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
memberIdYes
programRevisionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false; the description reinforces the idempotency contract by telling the agent to reuse the redemption ID on retry, which is real added value for a retry-prone mutation. It says nothing about side effects (points deduction, balance impact), failure modes, or whether a duplicate submission without the same ID double-redeems.

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?

Two short sentences, zero filler, with the core action front-loaded and the retry constraint appended. Nothing is redundant.

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 three-required-parameter destructive mutation with no output schema, the definition covers the action and the idempotent retry contract but leaves an agent unsure about side effects, error conditions, and how the redemption is tied to a specific reward. Annotations pick up part of the behavioural slack, so the remaining gaps are moderate rather than fatal.

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 burden; it does map 'member' to memberId and 'programme revision' to programRevision, and it explains the non-obvious role of 'id' as a client-supplied retry key. However, it never states that all three are UUIDs (the revision is an integer), and it never identifies which reward is being redeemed, which is the biggest semantic gap in the schema.

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?

States a specific verb and resource ('Record a reward redemption') with its scope ('for the specified member and programme revision'), which separates it from the neighbouring redeem_gift_card. It stops short of explicitly naming what distinguishes it from that sibling, but the reward/gift-card distinction is inferable 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The only guidance is a retry rule ('Reuse the redemption ID on retry'), which is genuinely useful invocation advice. There is no statement of prerequisites (e.g., member must have sufficient points), when not to use it, or how it relates to redeem_gift_card or get_loyalty_activity.

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.

Resources