Skip to main content
Glama

list_clients

Read-only

List the coach's clients (id, name, email). Use the returned _id as clientId/userId for other tools.

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

Input Schema

NameRequiredDescriptionDefault
pageSizeNo
pageNumberNo

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 the safety profile is covered. The description adds the return-field list and the ID-reuse contract, but says nothing about pagination defaults (pageSize 50, max 100) or whether results are truncated, which matters 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, zero filler; the core purpose is front-loaded and the field list and ID-reuse tip follow immediately. Nothing redundant relative to the schema or annotations.

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?

With no output schema, the partial return-field inventory is valuable, but it omits pagination semantics and total counts for a tool that caps at 100 results per page. For a plain list tool this is close to adequate, but the paging gap is a real omission.

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 both parameters, so the description carries the burden — and it says nothing about pageSize or pageNumber, not even that paging exists. The schema only supplies types, defaults and ranges, leaving the agent to guess that results may be paginated.

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 ('List the coach's clients') and enumerates the returned fields (id, name, email), which tells an agent what it will get back. It does not explicitly distinguish itself from siblings like list_clients_needing_onboarding or list_organization_clients, so the scope ('all clients for the coach') must be inferred.

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 second sentence gives a concrete downstream usage rule — reuse the returned _id as clientId/userId in other tools — which is genuinely useful. It offers no guidance on when to call this instead of the filtered siblings (needing_onboarding, pending_intake, organization clients), leaving selection to inference.

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.