Skip to main content
Glama

Loyal Spark Holder

Get Reward Workflow Status

get_reward_workflow_status
Read-onlyIdempotent

Autonomous status planner for recipients: returns current reward redemption step and machine-readable next_actions[] (check balance -> prepare transfer -> redeem -> voucher).

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": "get_reward_workflow_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
reward_idNoOptional specific reward UUID to focus the plan on.
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 declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuine value beyond that by disclosing the return shape (current step + next_actions[]) and the ordered workflow it plans against, which is behavioral information not present in structured fields.

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 front-loaded sentence that delivers the resource and the return contents with no padding; the step arrow chain efficiently conveys the workflow order. The only waste is the vague 'Autonomous status planner' framing.

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?

With no output schema, the description carries the burden of explaining return values, and it does identify the two key outputs (current step and next_actions[]). For a two-parameter read-only tool with full annotation coverage, this is nearly complete, though the concrete shape of next_actions entries is left unspecified.

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 100%, so both parameters (token_address, optional reward_id) are already documented in the schema with format and pattern constraints. The description adds no meaning about how reward_id narrows the plan versus the default program-wide view, so the baseline of 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 states a specific resource (reward redemption workflow status) and what it returns: the current step plus a machine-readable next_actions[] sequence. That is enough to distinguish it from siblings like redeem_my_reward or prepare_reward_redemption, though the leading phrase 'Autonomous status planner' is jargon that adds little.

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?

It scopes usage to 'recipients' and implies this is the entry point of a checkout flow by listing the ordered steps, so an agent can infer when to call it. However, it never explicitly says 'call this before prepare_reward_redemption' or names the sibling tools it hands off to, leaving the routing inference implicit.

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