NexRex

Current NexRex account

get_current_user

Read-onlyIdempotent

Identify the connected NexRex account: user_id, athlete_id, connection email, display name, roles and org_id. Takes no arguments and needs no coach role. Use it for 'who am I logged in as?' and before reading the account's own training: its athlete_id is the id athlete and plan tools take. A coach may not appear in their own athlete roster, so a roster miss says nothing about this account. org_id is the connection's organization context, not every membership; email is null when the connection supplied none.

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`email`	No
`error`	No
`roles`	No
`org_id`	No
`status`	No
`message`	No
`privacy`	No	Present when the athlete's settings withhold data.
`user_id`	No
`warnings`	No
`next_step`	No	What can be done next, for example after a failure.
`athlete_id`	No
`next_cursor`	No	Reads the next page; null on the last page.
`reason_code`	No
`total_weeks`	No
`display_name`	No
`user_content`	No	Fields in this result that people wrote.
`weeks_returned`	No
`truncated_fields`	No	Lists cut to fit one response: rows returned and total.
`generated_content`	No	Fields in this result that NexRex's AI wrote.
`profile_available`	No
`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.

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.8/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 behavior, and the description adds context they don't carry: zero arguments, no coach role required, email is null when the connection supplied none, and org_id is the connection's organization context rather than every membership. The roster-miss caveat also preempts a plausible false conclusion about the account's validity.

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 identity payload first, then usage triggers, then caveats, and every sentence carries distinct information. It is somewhat dense in the middle, but there is no filler or repetition of annotation facts.

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?

An output schema exists, yet the description still names the returned fields and interprets the tricky ones (org_id scope, nullable email), which is the right level of detail for a no-parameter identity tool. It also explains how the result feeds subsequent athlete/plan calls, closing the workflow gap.

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?

There are no parameters, so the baseline is 4, and the description correctly states that the tool 'takes no arguments,' removing any expectation of input. Nothing further is needed on the parameter side.

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 ('Identify the connected NexRex account') and enumerates the returned identity fields, so the agent knows exactly what it gets back. It also distinguishes itself from roster-based sibling tools by warning that a coach may not appear in their own athlete roster.

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 triggers ('who am I logged in as?' and before reading the account's own training) and a concrete prerequisite statement ('needs no coach role'), plus the key handoff that its athlete_id is the id the athlete and plan tools take. That covers when to call it and what to do with the result.

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?