Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

fanduel_racing_past_tracks

Retrieve FanDuel racing tracks with past results: filter by date for tracks and race types, by track for race dates, or list all available tracks.

Instructions

FanDuel Racing tracks with past results. Lists the tracks that have past results. With date it returns the tracks that ran that day with their race count and race types; with track it returns that track and the dates it ran (newest first, paged by page and limit, back to 2008); with neither it returns every track (786 on 2026-10-24). An unknown track returns 404.

Input Schema

NameRequiredDescriptionDefault
dateNoDay as `YYYY-MM-DD`, from `2008-01-01`
pageNoPage number, from 1; default 1, at most 10000
limitNoItems per page, 1 to 200; default 50
trackNoTrack code such as `BEL`; adds the dates the track ran

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

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 load and does well: it discloses paging behavior (page/limit, back to 2008), ordering (newest first), an exact corpus size, and a 404 on unknown track. It doesn't cover read-only status, rate limits, or response shape, so it stops one step short of full transparency.

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-loads what the tool returns before drilling into parameter modes, and every clause carries information. Slightly dense with the mid-sentence '786 on 2026-10-24' count and a mildly redundant first two sentences.

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?

No output schema exists, so the description must convey return shape, which it does per mode (race count and race types; dates newest-first, paged). Missing only granular return field detail and failure modes beyond the 404 case.

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, but the description goes beyond it by explaining the interaction effect of `date` vs `track` vs neither and by tying `track` to adding run dates. Page/limit semantics come from the schema, so the gain is real but partial.

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 ('Lists the tracks that have past results') and scopes it to past results, which distinguishes it from generic track listings. However it never names or contrasts the adjacent fanduel_racing_tracks / fanduel_racing_track / fanduel_racing_results siblings, so an agent must infer the boundary.

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?

Explicitly lays out the three invocation modes: with `date` (tracks that ran that day with race counts/types), with `track` (that track's run dates, newest first), and with neither (all tracks). This is effectively when-to-use guidance for its own parameters, though it stops short of naming alternative tools.

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