Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fanduel_racing_past_races

List past horse races by date and optional track, returning race number, post time, conditions, distance, purse, surface, and runner count; use the past-race route for results.

Instructions

FanDuel Racing past races of a day. Lists the races that ran on a date, at one track or at every track (558 races on 2026-10-02), with number, post time, conditions, distance, purse, surface and runner count; it has no results, so read a race with the past-race route. Results go back to 2008. A date with no races returns an empty list; today's date is empty until a race is official.

Input Schema

NameRequiredDescriptionDefault
dateYesDay as `YYYY-MM-DD`, from `2008-01-01`
pageNoPage number, from 1; default 1, at most 10000
limitNoRaces per page, 1 to 200; default 50
trackNoTrack code such as `BEL`; omit for every track

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations the description carries the burden and does so: it discloses the returned attributes, the read-only nature ('has no results'), the empty-list edge case, the live-day lag ('today's date is empty until a race is official'), and historical depth to 2008. It omits pagination behavior at scale (max page 10000) and any auth/rate-limit notes, which keeps it from a 5.

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?

Two dense sentences, front-loaded with the core action and immediately followed by the limitation and the redirect. Slight redundancy in restating the tool name ('past races of a day' then 'Lists the races that ran on a date'), but every clause otherwise earns its place.

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 the return shape, and it does by enumerating number, post time, conditions, distance, purse, surface and runner count. Edge cases (no races, ungraded today) and the outbound redirect are covered. Only pagination totals and the distinction from similarly named racing siblings are missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so date, page, limit and track are already documented with formats and ranges. The description only reinforces the track parameter implicitly ('at one track or at every track') and adds no format or semantics beyond the schema. Baseline 3 applies.

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 (lists the races that ran on a date) plus the returned fields, and distinguishes itself from the `past-race` detail route by declaring it has no results. An agent can identify its scope 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?

Explicitly routes the agent away: 'it has no results, so read a race with the `past-race` route' names the alternative and the condition. It also bounds usage to dates from 2008 onward and warns that today's date is empty. It stops short of positioning against the other racing list siblings (fanduel_racing_races / fanduel_racing_results).

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