NexRex

Team overview

get_team_overview

Read-onlyIdempotent

Get the current state of the coach's organization in one call: total athletes, each group with its group_id (used by get_group_info, list_group_plans and the other group tools) and member count, how many athletes need attention, and those athletes' flags and suggested actions. Use get_coach_athletes for the full per-athlete roster and get_coach_weekly_report for a completed week's report. Needs a coach or admin role.

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`atl`	No	Acute training load (fatigue, ~7-day load).
`ctl`	No	Chronic training load (fitness, ~42-day load).
`tsb`	No	Training stress balance (form): ctl minus atl.
`date`	No
`error`	No
`groups`	No
`org_id`	No
`status`	No
`message`	No
`metrics`	No
`privacy`	No	Present when the athlete's settings withhold data.
`org_name`	No
`attention`	No
`next_step`	No	What can be done next, for example after a failure.
`team_size`	No
`athlete_id`	No
`next_cursor`	No	Reads the next page; null on the last page.
`reason_code`	No
`total_weeks`	No
`user_content`	No	Fields in this result that people wrote.
`weeks_returned`	No
`not_shared_count`	No
`truncated_fields`	No	Lists cut to fit one response: rows returned and total.
`attention_details`	No
`generated_content`	No	Fields in this result that NexRex's AI wrote.
`session_definitions`	No	Sessions that several rows of this result share by session_ref.
`content_block_fields`	No	Column names of every content_blocks row, nested blocks rows included.
`attention_signal_basis`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 14, 2026

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."

First observedNov 12, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds context annotations cannot carry: the coach/admin authorization requirement and the fact that returned group_id values are the keys consumed by get_group_info and list_group_plans. It does not discuss pagination or freshness of the "current state", which keeps it off a 5.

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?

Front-loaded with the core action in the first clause, followed by what it returns, then alternatives, then the auth prerequisite. Three sentences, no filler, and the parenthetical about group_id earns its space by explaining downstream tool compatibility.

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?

With an output schema present, the description need not document return shapes in full, yet it summarizes the payload well enough for selection. Auth requirements, scope, sibling boundaries, and the group_id linkage are all covered, leaving nothing an agent needs in order to call this correctly.

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 zero parameters, so there is nothing the description must disambiguate and the baseline is 4. The description correctly spends no words on argument semantics and instead describes output content.

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 current state of the coach's organization") and then enumerates exactly what comes back: total athletes, groups with group_id and member counts, athletes needing attention, and their flags and suggested actions. It is clearly differentiated from get_coach_athletes and get_coach_weekly_report by name, so an agent can choose without opening either 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?

Explicitly routes the agent to alternatives with the selecting condition: get_coach_athletes for the full per-athlete roster and get_coach_weekly_report for a completed week's report. It also states the prerequisite (coach or admin role) and the "in one call" framing that makes this the aggregate summary rather than a detail lookup.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All NexRex tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?