Skip to main content
Glama

list_clients_needing_onboarding

Read-only

Clients whose onboarding checklist is still in progress — the coach's 'clients to set up' list. Each entry has the client, status and completed/total step counts.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/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 by structured data. The description contributes beyond that by disclosing return contents (client, status, completed/total step counts), but says nothing about ordering, pagination, or whether clients with zero recorded steps are included.

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, front-loaded with the defining filter condition, followed by the per-entry shape. Nothing is repeated from the title or annotations and no sentence is wasted.

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 zero-parameter, read-only list tool with no output schema, the description supplies both the selection criterion and the fields each entry carries, which is most of what an agent needs. Only edge-case behavior (empty results, ordering, result volume) is left unstated.

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?

The tool takes no parameters, so there is no parameter meaning to add and the schema imposes no interpretation burden. The description correctly spends its words on scope and return shape instead of inventing arguments.

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 resource (clients) plus a precise filter condition (onboarding checklist still in progress) and adds a plain-language gloss ('clients to set up'). It implicitly separates itself from generic list_clients, but never names the sibling that would return clients already onboarded, so differentiation is inferred rather than explicit.

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 'coach's clients to set up list' framing implies when an agent should reach for this tool, but there is no explicit when-not guidance and no named alternative (e.g. list_clients for the full roster, or the pending-intake variant). Usage must be inferred from the filter description.

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.