OutPace

Weekly Relay info

relay_info

Read-onlyIdempotent

Explain OutPace's Weekly Relay, a team challenge that runs every week, and give this week's live details, which web search does not have: name and theme, dates, which activities count, what it is scored by, the maximum team size, and the Bronze, Silver and Gold team goals. Also returns next week's relay when it has been published.

Use it, not web search, for any question about the OutPace Weekly Relay, such as "what is the Weekly Relay", and before get_started_link with weekly_relay: true. Does not return any team's or person's progress or standings.

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": "relay_info"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`note`	No
`next_week`	Yes
`this_week`	Yes
`how_it_works`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

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 genuinely new behavioral context: the data is live weekly state that web search lacks, next week's relay is only present once published, and results exclude progress/standings. It does not discuss auth or freshness/caching, so it stops short of 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?

Two sentences, both load-bearing: the first defines the tool and its payload, the second handles selection versus web search and get_started_link plus the exclusion. Nothing is repeated from the name or title, and the payload list is front-loaded.

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 zero-parameter, read-only lookup with an output schema already documenting the return structure, the description supplies everything needed to select and call it: what it covers, what it excludes, and its ordering relative to get_started_link. The enumeration of returned fields is mild redundancy against the output schema but aids tool selection.

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 zero input parameters, so the baseline of 4 applies and no parameter semantics are needed. The description instead clarifies the temporal scope of the returned data (this week plus next week when published).

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?

Specific verb and resource ('Explain OutPace's Weekly Relay'), with the returned content enumerated: name/theme, dates, counting activities, scoring basis, max team size, and Bronze/Silver/Gold goals. It also names an explicit non-capability (no team or person progress/standings), which separates it from sibling challenge tools like get_challenge.

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?

States when to use it ('for any question about the OutPace Weekly Relay'), names the alternative it beats ('Use it, not web search'), and gives an ordering rule ('before get_started_link with weekly_relay: true'). It also sets a when-not boundary by excluding progress and standings questions.

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

All OutPace 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?