Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

races_results

Fetches a runner's official race result by bib across RunSignup, Athlinks, or RaceRoster, returning times, pace, places, and splits in one schema.

Instructions

races: Result by bib. GET /v1/races/results. One runner's official result, by bib number, in one schema for all three platforms: names, chip and gun time, pace, overall, gender and age-group place, and splits where the platform publishes them. runsignup needs race_id and event_id. athlinks needs event_id and may take course_id (without it the event's courses are tried, largest first). raceroster needs event_id and may take course_id when a bib is used in more t Costs 1 credit when it succeeds. Errors, blocked or timed-out requests, invalid requests and cache hits cost nothing. A not-found or empty result is charged only where that operation's published cost says so.

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": {
      "platform": "<platform>",
      "event_id": "<event_id>",
      "bib": "<bib>"
    },
    "name": "races_results"
  }
}

Input Schema

NameRequiredDescriptionDefault
bibYesThe runner's bib number.
race_idNorunsignup only: the RunSignup race id.
event_idYesThe event or edition id from /v1/races/search or /v1/races/events.
platformYesTiming platform: runsignup, athlinks (also carries ChronoTrack events) or raceroster.
course_idNoathlinks and raceroster: the course or race within the event, from /v1/races/events.
cache_max_ageNoServe a cached response when it is newer than this. A cache hit costs 0 credits.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it discloses the credit model (1 credit on success; errors, blocked, timed-out, invalid requests and cache hits are free), the athlinks course-fallback behavior ('courses are tried, largest first'), and that splits are only present where the platform publishes them. The raceroster clause is cut off mid-sentence ('when a bib is used in t'), leaving that platform's behavior partially undisclosed.

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 purpose and endpoint, then platform requirements, then cost. Most sentences earn their place, but the pricing paragraph is long and the raceroster sentence is truncated, which slightly degrades structure and leaves an incomplete thought in the text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 6-parameter, 3-required tool with no annotations and no output schema, the description covers platform prerequisites, fallback behavior, cost accounting, and even enumerates returned fields (names, chip/gun time, pace, places, splits). The only real gap is the truncated raceroster clause.

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 baseline is 3, but the description adds real meaning beyond the schema by tying parameters to platforms: race_id is runsignup-only, course_id applies to athlinks and raceroster, and omitting course_id on athlinks triggers a largest-course-first fallback. That is operational semantics the schema alone does not convey.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Result by bib', GET /v1/races/results) and scopes it to 'one runner's official result, by bib number' unified across three platforms. An agent can distinguish it from races_search/races_events by scope, though no sibling is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear conditional usage context per platform: runsignup requires race_id and event_id, athlinks requires event_id and optionally course_id, raceroster similar. It does not name an alternative tool or state exclusions, so it stops short of explicit when-to-use/when-not-to-use routing.

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

Deploy Server

Other Tools