Skip to main content
Glama

Check Loyalty Tier & Free-Call Balance

check_loyalty
Read-onlyIdempotent

Loyalty tier and free-call balance for any XRPL wallet, derived from its settled 402Proof payment history. Automatic — no registration. Read-only. Free.

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": {
      "wallet": "<wallet>"
    },
    "name": "check_loyalty"
  }
}

Input Schema

NameRequiredDescriptionDefault
walletYesXRPL classic address (r...) of the wallet to look up

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / wallet / description
      Added value: +"XRPL classic address (r...) of the wallet to look up"
  2. 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 read-only, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavioral facts: no registration or setup is required, the call is free, and the result is derived from settled payment history rather than live state — important context for interpreting the answer.

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?

Two compact sentences, front-loaded with what is returned and for whom, followed by the key operational facts. Every phrase (derivation source, no registration, read-only, free) carries information; nothing is padding.

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?

For a one-parameter read tool with full annotation coverage this is nearly sufficient, but with no output schema the agent gets no sense of the return shape — what the tier values are, what unit the balance is in, or what a zero-balance response looks like. That gap keeps it at minimum-viable rather than complete.

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?

There is a single parameter with 100% schema description coverage ('XRPL classic address (r...)'), so the schema carries the burden and the baseline is 3. The description's 'any XRPL wallet' adds only a mild clarification that arbitrary wallets, not just the caller's, can be queried.

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 resource precisely (loyalty tier and free-call balance) and its scope (any XRPL wallet), plus the data source (settled 402Proof payment history), which implicitly separates it from the bureau/attestation siblings. It never names an alternative explicitly, so it stops short of a 5.

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: 'Automatic — no registration' and 'Free' tell the agent it can call it freely, but there is no explicit statement of when to prefer this over bureau_public_score or get_agent_passport, nor any when-not condition. An agent must infer the selection rule from the resource name.

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