Skip to main content
Glama

Loyal Spark Holder

List Rewards For Program

list_rewards_for_program
Read-onlyIdempotent

List active rewards you can redeem for a program where your wallet has loyalty activity or balance.

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": {
      "token_address": "<token_address>"
    },
    "name": "list_rewards_for_program"
  }
}

Input Schema

NameRequiredDescriptionDefault
token_addressYesLoyalty program token contract.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and closed-world behavior, so the bar is lower. The description still adds real behavioral context by disclosing an eligibility gate — results are limited to programs where the wallet has loyalty activity or balance, implying an empty result for unrelated programs. It omits return format and pagination, which keeps it below a 5.

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?

One sentence with no wasted preamble, and the eligibility constraint is packed in rather than buried. The nested 'program where your wallet has...' phrasing makes it slightly denser to parse than necessary.

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 list tool with full annotations and no output schema, the definition covers what the tool does and who is eligible to see results. The main residual gap is that 'reward' itself is undefined and no hint is given about result shape or ordering, which matters since no output schema exists.

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 parameter is already documented as a loyalty program token contract with an address pattern, so the schema does the heavy lifting. The description only reinforces that the address identifies the program whose rewards are filtered, adding marginal meaning beyond 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?

The description gives a specific verb and resource ('List active rewards') scoped to a single program, which separates it from siblings like redeem_my_reward or get_reward_workflow_status. It stops short of naming an alternative readers should consider, so the differentiation is inferred from semantics rather than stated.

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?

Usage is only implied: an agent can infer this is the discovery step before prepare_reward_redemption or redeem_my_reward, but the description never says so. There is no explicit when-to-use, when-not-to-use, or statement of prerequisites beyond the eligibility clause.

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