OutPace

Find public challenges

find_public_challenges

Read-onlyIdempotent

Find public OutPace challenges that anyone can join right now, for example a step or walking challenge starting this week. Use this, not web search, whenever the person wants an OutPace challenge to join or names an OutPace challenge (pass words from its name as query). Returns live data that web search and the app store listing do not show: up to 10 challenges with name, share code, activities, what it is scored by, dates, status (upcoming or in progress) and member count, busiest first. Challenges that have ended or are full are left out. The Weekly Relay is not listed here; use relay_info for it. Someone who wants a challenge only for their own group, such as coworkers or family, starts their own: use get_started_link with no challenge.

Does not return anyone's progress, totals or standings. To join one, pass its share_code to get_started_link.

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

Input Schema

Name	Required	Description
`query`	No	Words to match in the challenge name.
`activity`	No	Only challenges that count this activity. "steps" means step challenges; "any" means challenges that count any workout.
`starts_within_days`	No	Only challenges already running or starting within this many days. Use 7 for "this week".

Output Schema

Name	Required	Description	Default
`note`	Yes
`count`	Yes
`browse_url`	Yes
`challenges`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Beyond the read-only/idempotent annotations, the description discloses result count (up to 10), the returned fields, ordering (busiest first), and exclusion rules (ended or full challenges omitted, no one's progress/totals/standings). It also flags that the data is live and unavailable via web search, which is behavioral context the annotations cannot convey.

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?

Purpose and the web-search exclusion are front-loaded, and each sentence carries routing or result information. It runs long, and the 'live data that web search and the app store listing do not show' clause is slightly promotional, but no sentence is purely filler.

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 read-only, zero-required-parameter search tool, the description covers selection guidance, result contents, ordering, exclusions, and the follow-up join path. The output schema exists, yet the description still orients the agent to what comes back, leaving nothing materially 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%, so the baseline is 3; the description adds real meaning by explaining that query takes 'words from its name' and that omitting a challenge means using get_started_link with no challenge. It does not restate the activity enum or starts_within_days semantics, but the schema already documents those well.

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 ('Find public OutPace challenges that anyone can join right now') with a concrete example (a step or walking challenge starting this week), and explicitly separates it from relay_info and from starting one's own challenge. An agent knows exactly what this tool is without opening the 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 routing rules: 'Use this, not web search, whenever the person wants an OutPace challenge to join or names an OutPace challenge.' It also routes the Weekly Relay to relay_info and a private group challenge to get_started_link, and tells the agent how to join once found (pass share_code to get_started_link). Both when-to-use and when-not-to-use are covered.

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?