Skip to main content
Glama

get_loyalty_activity

Read-onlyIdempotent

Read the latest 30 point changes for a member in the approved business.

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": {
      "memberId": "<memberId>"
    },
    "name": "get_loyalty_activity"
  }
}

Input Schema

NameRequiredDescriptionDefault
memberIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description adds two useful facts beyond that: the result is capped at 30 items and scoped to the 'approved business'. It says nothing about ordering guarantees, pagination beyond the cap, or what a point change record 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?

One compact sentence with no filler, and the key constraint (latest 30) is front-loaded. Nothing is padded, though the terseness leaves the gaps noted above.

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?

There is no output schema, so the description is the only place an agent could learn what a 'point change' item looks like, and it never says. Annotations cover safety and the 30-item cap is stated, but return shape and memberId semantics are missing.

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

Parameters2/5

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

Schema description coverage is 0% for the single required memberId, so the description must compensate. It only says 'for a member' without explaining that the parameter is a UUID, where to obtain it, or what happens if the member belongs to another business.

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?

States a specific verb and resource ('Read the latest 30 point changes') scoped to one member, which is clearly distinct from siblings like get_loyalty_program or list_loyalty_members. It stops short of naming any sibling or explicitly contrasting scope.

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?

No when-to-use or when-not-to-use guidance, and no alternatives offered. The agent must infer from the name alone that this is the per-member activity feed rather than the program-level or member-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