Skip to main content
Glama

Loyal Spark Holder

Redeem My Reward

redeem_my_reward

Redeem a reward into an active voucher after paying the token cost on-chain (requires transfer tx hash).

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": {
      "reward_id": "<reward_id>",
      "transaction_hash": "<transaction_hash>"
    },
    "name": "redeem_my_reward"
  }
}

Input Schema

NameRequiredDescriptionDefault
reward_idYesReward UUID from list_rewards_for_program.
transaction_hashYesOn-chain transfer tx paying the reward token cost.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent operation, so the safety profile is covered. The description adds the meaningful context that an on-chain payment must precede the call and that the result is an activated voucher, but says nothing about whether the reward is consumed, what happens on retry or failure, or what is returned.

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 sentence with the action front-loaded and the prerequisite in parentheses. Nothing is wasted and no scrolling is needed to grasp the operation.

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 two-parameter, fully documented mutation with a clear outcome and annotations covering safety and idempotency, this is close to complete. The main gap is the absence of any statement about the returned voucher or about retry semantics for a non-idempotent redemption.

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 coverage is 100%, and the schema descriptions already explain both parameters, including the pointer to list_rewards_for_program and the 0x hash pattern. The description only restates the tx-hash requirement, adding no meaning beyond the structured fields, so the baseline 3 applies.

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 ('Redeem a reward') plus the concrete outcome ('into an active voucher'), which is more than the name alone conveys. It implies the ordering relative to prepare_reward_redemption via 'after paying the token cost on-chain' but never names that sibling, so differentiation is inferential rather than explicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

It clearly states the precondition for use: the token cost must already be paid on-chain and the tx hash supplied. There are no explicit exclusions or named alternatives (e.g., prepare_reward_redemption for the earlier step, get_reward_workflow_status for checking progress), so it falls short of a full when/when-not treatment.

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