Skip to main content
Glama

get_client_roster

Read-only

Every client sorted into segments (NEEDS_PROGRAMMING, INACTIVE, NEW, PLAN_ENDING, ON_TRACK) with last activity, 7/30-day workout adherence and plan-end countdown. Best first call for 'who needs attention?'. Rows carry clientId only — join names with list_clients.

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": "get_client_roster"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/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 real value by disclosing the field-level payload and the important limitation that rows carry clientId only, with names requiring a join to list_clients. However, it does not say whether all clients are always returned or whether very large rosters are truncated, so ordering/completeness behavior remains unstated.

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 dense sentences: the first front-loads the payload, the second front-loads usage and the join caveat. Every clause carries information; nothing is repeated from the title or annotations.

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?

With no output schema, the description is the only source of return-value information and it does list the segment taxonomy and metrics, plus the clientId-only caveat, which is enough to call and use the tool. It stops short of describing row shape/ordering or whether the segment field is a single value or a list, which leaves minor ambiguity.

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?

Zero parameters, so there is no parameter semantics to explain; the baseline of 4 applies. The description correctly implies the call is unscoped (no filtering arguments), matching the empty schema.

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 ('Every client sorted into segments') and enumerates the exact segment values plus the metrics returned (last activity, 7/30-day adherence, plan-end countdown). This is clearly distinguishable from siblings like get_client_daily_metrics or list_clients.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly positions itself as 'Best first call for who needs attention?', giving a concrete triggering question, and routes the agent to list_clients when names are needed. The join caveat doubles as a sequencing instruction.

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.