Skip to main content
Glama

rewards_balance

Read-only

Retrieve a card's reward balance, including points earned from purchases, manual adjustments, and the balance's rupee value.

Instructions

Reward balance per card: earned from purchases, plus or minus manual adjustments, and what the balance is worth in rupees.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "rewards_balance"
  }
}

Input Schema

NameRequiredDescriptionDefault
cardNoCard id or name

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes that this is a safe read, so the bar is lower. The description usefully clarifies that the returned balance includes both earned amounts and manual adjustments and is converted to rupees, which is real semantic content beyond the annotation, but it says nothing about scope when no card is supplied, pagination, or freshness of the balance.

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 filler, and the subject ('reward balance per card') is front-loaded. The 'plus or minus manual adjustments' clause is slightly wordy but it is the piece that explains the balance composition, so it earns its place.

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 an output schema present, the description need not explain return values, and for a single-optional-parameter read tool the conceptual framing is largely sufficient. The only meaningful gap is whether omitting the card returns balances for all cards, which an agent would need to know before calling.

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 optional 'card' parameter is documented in the schema as 'Card id or name'. The description's phrase 'per card' reinforces that scoping but adds no format or id-vs-name detail, and leaves the omitted-card behavior unstated. Baseline 3 applies when the schema does the heavy lifting.

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 names a specific resource and its composition: reward balance per card, split into purchase earnings, manual adjustments, and rupee valuation. It is clear what the tool returns, but it uses a noun phrase rather than a verb and does not contrast itself with adjust_rewards, which touches the same balance data.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance and no mention of alternatives, even though adjust_rewards is a closely related sibling that modifies the very balance this tool reports. The agent must infer from the name alone that this is the read path and that one is the write path.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.