Skip to main content
Glama

Loyal Spark Holder

Prepare Reward Redemption

prepare_reward_redemption

One-shot planner: returns B20/ERC-20 transfer calldata for the reward token cost plus the recipient_reward workflow so the agent can broadcast the tx and then call redeem_my_reward.

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>"
    },
    "name": "prepare_reward_redemption"
  }
}

Input Schema

NameRequiredDescriptionDefault
reward_idYesReward UUID from list_rewards_for_program.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and idempotentHint=false, so the agent knows this writes state, yet the description does not explain what state is created, whether a workflow expires, or what a repeat call does. It does add the important fact that the tool returns calldata rather than broadcasting. The phrase 'one-shot planner' hints at single-use semantics but is ambiguous.

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 sentence with no filler, and the key output (transfer calldata) is front-loaded after the 'one-shot planner' label. Density comes at some cost to readability, since several concepts are compressed into one clause.

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 one-parameter preparation tool with no output schema, the description covers the return payload and the follow-up call, which is what an agent needs to sequence correctly. Gaps around workflow lifetime and the idempotency implication are minor but real.

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 single reward_id parameter is documented in the schema with its source (list_rewards_for_program). The description implies the reward determines the token cost but adds no format, constraints, or error conditions beyond the schema, 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?

States a specific action and output: 'returns B20/ERC-20 transfer calldata for the reward token cost plus the recipient_reward workflow'. An agent can tell this prepares a transaction rather than executing it, and the mention of redeem_my_reward positions it relative to a sibling. The term 'recipient_reward workflow' is internal jargon that isn't defined, which keeps it from 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 Guidelines4/5

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

Gives a concrete sequence: broadcast the returned calldata, then call redeem_my_reward. That is real when-to-use guidance. It stops short of exclusions - it never says when to prefer prepare_loyalty_token_transfer or what to do if a workflow is already pending.

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