Skip to main content
Glama

get_rewards_program

Get one rewards/players-club program by id — brand, earning rules, status-match notes, and full tier ladder. Tiers carry confirmed_at and the ladder carries tier_ladder_freshness.state; an unconfirmed or stale threshold has not been checked against the program's published terms, so report it as such. (get_casino also returns a casino's program inline.)

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

Input Schema

NameRequiredDescriptionDefault
idYesRewards program id (UUID), from list_rewards_programs

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the disclosure burden and does so for the most consequential part: it explains that `confirmed_at` on tiers and `tier_ladder_freshness.state` on the ladder mean the threshold may be unchecked against published terms, and instructs the agent to report it as such. It does not cover error behavior for an unknown id or any auth/rate-limit expectations.

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?

Front-loaded with purpose and return contents, then the freshness caveat, then the sibling pointer — no filler. The backticked field names make the second sentence dense, but every clause carries information an agent needs to interpret the response.

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 must convey return shape, and it names the top-level sections plus the two freshness fields that require interpretive caution. It stops short of describing the tier ladder's structure or what earning rules look like, but is sufficient to call and interpret the result correctly.

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?

One parameter at 100% schema coverage, and the schema already states it is a UUID sourced from list_rewards_programs. The description adds nothing about the id beyond what the schema provides, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Get one rewards/players-club program by id') and enumerates what comes back: brand, earning rules, status-match notes, tier ladder. The parenthetical naming get_casino as an inline alternative differentiates it from the most confusable sibling.

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?

Clear context for use (fetch a single program by id, with the id sourced from list_rewards_programs) and an explicit pointer that get_casino returns a casino's program inline, which lets an agent avoid a second call. No explicit when-not guidance, but the routing signal is present.

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.