Skip to main content
Glama

Loyal Spark Holder

List My Loyalty Balances

list_my_loyalty_balances
Read-onlyIdempotent

All loyalty token balances and tier levels for the holder wallet linked to this rwk_ key.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/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 meaningful scoping context that the annotations do not: results are derived from the holder wallet bound to the rwk_ key, i.e. auth determines the data set. It says nothing about ordering, emptiness, or what a 'tier level' contains.

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?

A single front-loaded sentence fragment with no filler; the resource and its scope appear immediately. It is efficient, though it stops short of being a complete sentence and could carry one more clause of guidance at no real cost.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no parameters and rich annotations, most of what an agent needs is present. However, there is no output schema, so the description is the only place to explain the return shape (per-token balance entries, tier data, empty-list behavior), and it does not.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is no parameter meaning to convey and the baseline is 4. The mention of the rwk_ key usefully clarifies that identity is supplied out-of-band via authentication rather than as an argument.

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 the specific resource returned (loyalty token balances plus tier levels) and scopes it to the holder wallet linked to the rwk_ key. The word 'All' implicitly distinguishes it from the singular get_my_loyalty_balance sibling, though it does not name that sibling explicitly.

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: 'All' suggests this is the plural/bulk counterpart to the single-balance tool, and the rwk_ scoping hints at authenticated holder context. There is no explicit statement of when to choose this over get_my_loyalty_balance or the other list_* tools.

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