Skip to main content
Glama

Coach athlete roster

get_coach_athletes
Read-onlyIdempotent

Get the coach's athlete roster, one row per athlete with basic info and attention flags, up to limit per page. Use it to pick or page through athletes; get_team_overview gives per-group totals and get_coach_weekly_report the stored report of a completed week. Flagged athletes come first, most severe first; total, needing_attention, urgent_count and watchlist_count cover the whole roster, and next_cursor reads the next page. Flags reflect plan compliance and absence, not physiological fatigue. Needs a coach or admin role. The coach may not be in this roster; get_current_user identifies the connected account.

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

Input Schema

NameRequiredDescriptionDefault
limitNoAthletes per page, 1-100.
cursorNonext_cursor from the previous page of this tool called with the same arguments; omit for the first page.

Output Schema

NameRequiredDescriptionDefault
countNo
errorNo
totalNo
org_idNo
statusNo
messageNo
privacyNoPresent when the athlete's settings withhold data.
scannedNo
athletesNo
org_nameNo
returnedNo
warningsNo
next_stepNoWhat can be done next, for example after a failure.
team_sizeNo
truncatedNo
athlete_idNo
next_cursorNoReads the next page; null on the last page.
reason_codeNo
total_weeksNo
urgent_countNo
user_contentNoFields in this result that people wrote.
flagged_countNo
returned_countNo
total_athletesNo
weeks_returnedNo
watchlist_countNo
not_shared_countNo
truncated_fieldsNoLists cut to fit one response: rows returned and total.
generated_contentNoFields in this result that NexRex's AI wrote.
needing_attentionNo
session_definitionsNoSessions that several rows of this result share by session_ref.
content_block_fieldsNoColumn names of every content_blocks row, nested blocks rows included.
attention_signal_basisNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / content_block_fields / description
      Previous value: -"Column names of every content_blocks row."New value: +"Column names of every content_blocks row, nested blocks rows included."
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses ordering ('Flagged athletes come first, most severe first'), the semantics of the flags ('plan compliance and absence, not physiological fatigue'), that counts cover the whole roster rather than the page, and the coach-or-admin role requirement. These are behavioral facts an agent cannot infer from structured fields.

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?

Front-loaded with purpose, then alternatives, then ordering, then auth. Four dense sentences with essentially no filler, though the paging and count details make it slightly heavy for a two-parameter read.

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

Completeness5/5

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

Output schema exists, so return values needn't be spelled out, and the description still explains ordering, whole-roster aggregate counts, and flag meaning. Auth requirements and the coach-not-in-roster caveat close the remaining gaps for a simple paged read.

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 100%, so limit (1-100) and cursor semantics are already documented, including that the cursor must come from the same arguments. The description adds only light reinforcement ('up to `limit` per page', '`next_cursor` reads the next page'), so the baseline 3 applies.

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 ('Get the coach's athlete roster') plus the row shape ('one row per athlete with basic info and attention flags') and page bound. It explicitly separates itself from get_team_overview (per-group totals) and get_coach_weekly_report (stored weekly report), so an agent can discriminate it without opening a schema.

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?

Gives explicit when-to-use ('pick or page through athletes') and names two alternatives with the conditions that select them. It also routes identity questions to get_current_user ('The coach may not be in this roster'), covering an edge case an agent would otherwise get wrong.

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.

Resources