Skip to main content
Glama

Race details

get_race_info
Read-onlyIdempotent

Look up one race in the NexRex race catalog by its catalog race_id: name, date and timezone, type, distance and course format. Use it for details of an athlete's goal race before planning around it. Races an athlete has already run (get_account_summary race history) are results, not catalog entries; their name, date, distance and finish time are in that history.

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": {
      "race_id": "<race_id>"
    },
    "name": "get_race_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
race_idYesA race catalog id, such as the race_id of a goal race in get_athlete_profile goals.

Output Schema

NameRequiredDescriptionDefault
raceNo
errorNo
statusNo
messageNo
privacyNoPresent when the athlete's settings withhold data.
race_idNo
warningsNo
next_stepNoWhat can be done next, for example after a failure.
athlete_idNo
next_cursorNoReads the next page; null on the last page.
reason_codeNo
total_weeksNo
user_contentNoFields in this result that people wrote.
weeks_returnedNo
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.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds the meaningful behavioral distinction that this is a catalog lookup rather than a results lookup, plus the field set returned. It does not discuss permissions or error behavior, but for a read-only catalog fetch that is a minor omission.

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?

Three tight sentences, each earning its place: identity/fields first, use case second, the disambiguation against results last. No filler or restatement of the title beyond what is needed.

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, read-only lookup with an output schema and fully annotated behavior, the description covers purpose, sourcing of the id, and the main misuse risk. Nothing an agent needs to call it correctly is missing.

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?

Schema coverage is 100% and the single parameter is already documented, so the baseline would be 3; the description adds value by specifying it must be a catalog race_id and that such ids appear in get_athlete_profile goals, which helps the agent source a valid value. It stops short of format or example values.

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 one race in the NexRex race catalog by its catalog race_id') and enumerates the fields returned (name, date and timezone, type, distance, course format). It also draws a clear line against get_account_summary race history, so an agent can distinguish it from the sibling without opening schemas.

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 an explicit when-to-use ('details of an athlete's goal race before planning around it') and an explicit when-not-to-use with the alternative named ('Races an athlete has already run ... are results, not catalog entries'). That is the full when/when-not/alternative triplet.

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