Skip to main content
Glama

lookup_gym_member

Read-only

Find a gym member by name or phone digits (phone shown masked, last 4 only), with whether their membership is active and when it ends. Use the clientId with other tools.

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": {
      "organizationId": "<organizationId>",
      "query": "<query>"
    },
    "name": "lookup_gym_member"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes
organizationIdYesGym/organization _id (from list_my_organizations)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Goes beyond the readOnlyHint/openWorldHint annotations by disclosing the privacy behavior (phone shown masked, last 4 only) and what the result conveys (active status and membership end date). It omits the 50-result cap and multi-match behavior, so the behavioral picture is good but not complete.

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 tight sentences that front-load the lookup keys, then the result shape, then the follow-on action. Nothing is redundant or padded.

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

Completeness4/5

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

For a read-only lookup with no output schema, the description supplies the essential return contract (masked phone, active flag, end date, clientId) and the follow-on workflow. Only the result-count limit and ambiguity handling are left undescribed.

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?

Schema coverage is only 33%, and the description compensates for the most important gap by defining what `query` accepts — a name or phone digits, including partial last-4 phone matching. The `limit` parameter remains unexplained in both schema and description, which keeps it short of a 5.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Find a gym member') plus the two lookup keys (name or phone digits), which cleanly separates it from get_gym_member_record (an id-based fetch) and the write-oriented member tools. An agent can pick this tool without opening the schema.

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?

The closing sentence 'Use the clientId with other tools' gives downstream guidance but not selection guidance: it never says when to prefer this over get_gym_member_record, nor what to do when multiple members match or nothing matches. Usage is implied rather than stated.

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.