Skip to main content
Glama

list_loyalty_members

Read-onlyIdempotent

Find loyalty members by name or membership reference and read their point balances. Use a narrower search if more results exist.

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

Input Schema

NameRequiredDescriptionDefault
searchNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile needs no restatement. The description does add two useful behavioral facts beyond that: the tool returns point balances, and the result set may be larger than what is shown. It omits result limits and how to retrieve the remainder, which is the main behavioral unknown for a list tool.

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?

Two sentences, front-loaded with the capability and followed by the workflow hint, with no filler. The second sentence is slightly imprecise ("narrower" without naming the parameter) but still earns its place.

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 rich annotations and no output schema, the description covers purpose, matched fields, and returned data adequately. It falls short on the one thing it raises itself: what happens when more results exist, since there is no pagination parameter to continue with.

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 0%, so the description must carry the parameter meaning, and it does partially by explaining that the search matches either a name or a membership reference. It does not address the empty-string default, the 120-character cap, or whether partial matching is supported.

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 pairs a specific verb ("Find ... and read") with a specific resource (loyalty members) and even names the returned data (point balances). It is clearly distinct from the nearest sibling, get_loyalty_activity, though it does not explicitly state that distinction.

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?

"Use a narrower search if more results exist" implies a lookup-then-refine workflow, which is real guidance, but it never names an alternative tool or a when-not condition. It also leaves the mechanism of "narrower" unspecified even though the only knob is the single `search` string.

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