Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

races_events

List a race's events and course IDs across RunSignup, Athlinks, or RaceRoster so you can query official results by the returned event identifiers.

Instructions

races: List a race's events. GET /v1/races/events. Lists the distances of a race and the ids /v1/races/results needs. runsignup: pass race_id; every finished event of the race is listed, each with its event_id. athlinks: pass event_id (an edition from /v1/races/search); its courses are listed with course_id. raceroster: pass event_id (a results code or a numeric event id); its races are listed with course_id. An empty list costs 0 credits. Costs 1 credit when it succeeds. Costs 0 credits when events is empty. 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>"
    },
    "name": "races_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
race_idNorunsignup only: the RunSignup race id.
event_idNoathlinks and raceroster: the event id.
platformYesTiming platform: runsignup, athlinks (also carries ChronoTrack events) or raceroster.
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/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full behavioral burden and does so: it discloses the credit cost model (1 credit on success, 0 on empty, errors/timeouts/invalid requests/cache hits free), cache behavior, and the exact per-platform return contents including the id fields returned. This is well beyond what a bare 'list events' statement would convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose and platform routing are front-loaded, which is good, but the cost discussion sprawls across four sentences with overlap ('Costs 0 credits when events is empty' vs. 'An empty list costs 0 credits' vs. the closing not-found sentence). That redundancy dilutes an otherwise tight definition.

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 four-parameter, no-output-schema lookup tool spanning three platforms, the description covers everything an agent needs: which parameter selects which platform, what each platform returns, downstream id usage, and the credit/caching implications. Nothing material 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 already 100%, so the baseline is 3; the description still adds value by explaining what an event_id actually is in each platform context (an edition from search vs. a results code or numeric id) and how the returned ids are consumed downstream. The cache_max_age parameter is only echoed from the schema, not elaborated.

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 ('List a race's events') plus the underlying endpoint, then immediately clarifies what is actually listed per platform (distances + ids for runsignup events, courses with course_id for athlinks, races with course_id for raceroster). An agent can distinguish this from results/search retrieval 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 Guidelines4/5

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

Gives explicit conditional guidance: use race_id for runsignup, event_id for athlinks (edition from /v1/races/search) and raceroster (results code or numeric id), and notes the ids feed /v1/races/results. It lacks an explicit negative case (e.g., 'if you already have event_id and want results, use races_results instead'), but the routing implications are clear.

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