Skip to main content
Glama

Loyal Spark Holder

Get My Loyalty Balance

get_my_loyalty_balance
Read-onlyIdempotent

Balance and tier for one loyalty program token held by the authenticated recipient wallet.

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_my_loyalty_balance"
  }
}

Input Schema

NameRequiredDescriptionDefault
token_addressYesLoyalty program B20/ERC-20 contract on Base.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description still adds real context beyond them by stating the lookup is bound to the authenticated recipient wallet, telling the agent it cannot query arbitrary wallets and needs no address argument.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with the resource first and the wallet scoping second; no filler, no repetition of the title.

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 read tool with full schema coverage and rich annotations, this is nearly sufficient, and the description even hints at the return payload (balance and tier). It falls just short of 5 only because it does not say what happens when the wallet holds no token for that contract.

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%, and the schema already documents the required token_address with a pattern and 'B20/ERC-20 contract on Base' meaning. The description only restates 'loyalty program token' without adding address format or chain guidance, so 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?

Names a specific resource pair (balance and tier) scoped to 'one loyalty program token' held by the authenticated wallet, which implicitly contrasts with the plural list_my_loyalty_balances. A sibling is not named explicitly, so the differentiation is inferred 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?

The phrase 'one loyalty program token' implies this is the single-token lookup versus a listing call, but there is no explicit when-to-use guidance, no stated prerequisites, and no named alternative for multi-token or cross-wallet queries.

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