Skip to main content
Glama

list_organization_clients

Read-only

List an organization's clients, optionally filtered by location or coach.

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>"
    },
    "name": "list_organization_clients"
  }
}

Input Schema

NameRequiredDescriptionDefault
coachIdNo
pageSizeNo
locationIdNo
pageNumberNo
organizationIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds nothing about pagination behavior, ordering of results, or what happens when a filter matches nothing — meaningful gaps given the schema exposes pageSize (default 50, max 100) and pageNumber. No contradiction with annotations, so it sits at an adequate 3.

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?

A single well-formed sentence with the resource front-loaded and the filtering caveat trailing it; nothing is redundant. It is efficient, though efficiency here partly reflects under-specification.

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

Completeness2/5

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

With five parameters at 0% schema coverage, no output schema, and only two of the five parameters addressed, the definition is thin for the tool's complexity. An agent cannot tell the required organizationId, the pagination limits, or how many results to expect without reading the raw schema.

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 carries the full burden. It explains what locationId and coachId filter on, which is genuine added meaning, but says nothing about the required organizationId, pageSize, or pageNumber, leaving three of five parameters undocumented anywhere.

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 an organization's clients") and adds scope via the optional location/coach filters. It is clear enough to distinguish from mutation siblings like bulk_invite_clients or add_offline_clients, but it never names the near-identical list_clients sibling, so the agent must infer the difference.

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 mention of optional location and coach filters implies when the filters are useful, but there is no explicit when-to-use, when-not-to-use, or pointer to an alternative such as list_clients for cross-organization listing. Guidance is present only by implication.

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.