Skip to main content
Glama

list_customer_pass_uses

Read-onlyIdempotent

List recorded uses and returns for a customer pass, newest first, including prior membership periods.

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": {
      "id": "<id>"
    },
    "name": "list_customer_pass_uses"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare this a safe, idempotent, closed-world read. The description adds real context beyond them — newest-first ordering and inclusion of prior membership periods — but says nothing about pagination limits or how much history is returned even though an offset parameter exists.

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, scope, and ordering, and no redundant or filler wording.

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 simple read-only list tool with no output schema, this covers purpose, ordering, and historical scope adequately. The gap is result-set behavior: nothing explains the offset/paging semantics or whether prior-period entries span the full history.

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%, so the description needed to explain the two parameters. It implies a customer pass identifier but does not state that id refers to the pass (not the customer), and it never mentions offset or paging behavior, so the low-coverage schema is not compensated for.

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 states a specific verb and resource ("List recorded uses and returns for a customer pass") and adds scope and ordering, which clearly separates it from the mutation siblings record_customer_pass_use and return_customer_pass_use. It stops short of explicitly naming an alternative, so it is clear but not fully differentiated.

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: the phrase "recorded uses and returns" suggests auditing a pass's history, but there is no statement of when to call this versus, e.g., issue_customer_pass or the record/return tools. No prerequisites or exclusions are given.

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