Skip to main content
Glama

Find an athlete

find_athlete
Read-onlyIdempotent

Look up athletes in the coach's organization by display name (partial match) or exact email. Returns matches with user_id, name and group names, to resolve a name before athlete tools or to answer which group an athlete is in; total_matches and truncated state any cap. Needs a coach role. No match means not in this roster, not that no account exists. get_current_user identifies the connected account.

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": {
      "query": "<query>"
    },
    "name": "find_athlete"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesPart of a display name, or an exact email address.

Output Schema

NameRequiredDescriptionDefault
errorNo
org_idNo
statusNo
matchesNo
messageNo
privacyNoPresent when the athlete's settings withhold data.
org_nameNo
warningsNo
next_stepNoWhat can be done next, for example after a failure.
truncatedNo
athlete_idNo
next_cursorNoReads the next page; null on the last page.
reason_codeNo
total_weeksNo
user_contentNoFields in this result that people wrote.
total_matchesNo
weeks_returnedNo
searched_membersNo
truncated_fieldsNoLists cut to fit one response: rows returned and total.
generated_contentNoFields in this result that NexRex's AI wrote.
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.

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?

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the remaining burden is auth, caps, and result semantics — all covered. The description discloses the coach-role requirement, the result cap signalled by `total_matches` and `truncated`, and the crucial interpretation caveat that no match means not in this roster rather than no account existing.

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 the core action and match modes, then prerequisites and caveats. Every clause carries information, though the semicolon-chained single paragraph is dense and the return-field listing is partly redundant with the output schema.

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?

For a one-parameter lookup with an output schema, everything an agent needs is present: matching semantics, auth requirement, cap signalling, negative-result interpretation, and a pointer to the sibling for account identity. Nothing material is missing.

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 coverage is 100% and the single `query` parameter is already documented as 'Part of a display name, or an exact email address.' The description restates the same partial-vs-exact distinction with no additional syntax, escaping, or format guidance, so it adds little beyond the schema — baseline 3.

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 ('Look up athletes'), the scope ('in the coach's organization'), the two match modes ('display name (partial match) or exact email'), and the return contents. An agent can distinguish it from get_athlete_profile or get_current_user without opening any 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 cases ('to resolve a name before athlete tools or to answer which group an athlete is in'), a prerequisite ('Needs a coach role'), and an explicit exclusion/redirect ('get_current_user identifies the connected account'). It also warns about misinterpreting a negative result, which is the main usage pitfall.

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