Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fanduel_racing_horse

Retrieve a FanDuel Racing horse's career record and past race results, including finishes, beaten lengths and starting prices, by supplying the horse id from search.

Instructions

FanDuel Racing horse career. Returns a horse's career record (starts, wins, top-three finishes, win percentage) and its past races newest first, each with the race conditions and the horse's own result line: finish position, post-race report, beaten lengths and starting price when the track reports them. Needs the horse's id from the search route; an unknown id returns 404.

Input Schema

NameRequiredDescriptionDefault
idYesHorse id (`id` of a `runner` result of the `search` route), such as `1002257`
pageNoPage of races, from 1; default 1, at most 10000
limitNoRaces per page, 1 to 200; default 50

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A4.5/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 so well: it discloses ordering ('newest first'), conditional field presence ('when the track reports them'), and the 404 failure mode for bad ids. It does not discuss rate limits or whether the response is paginated in the description itself, leaving that to the schema.

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

Conciseness5/5

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

Three short sentences, front-loaded with the tool's identity and return shape, then prerequisites and failure mode. Every clause carries information; nothing is repeated from the schema verbatim.

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?

There is no output schema, so describing return fields was mandatory and the description does it thoroughly, including field-level caveats and pagination-by-default implied by page/limit. Combined with the 404 note and id provenance, an agent has everything needed to invoke it correctly.

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; the description exceeds it by explaining id provenance ('`id` of a `runner` result of the `search` route'), which the schema's parenthetical echoes only briefly. It does not add anything about page/limit beyond the schema, which is acceptable since those are fully documented.

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?

The description opens with a specific verb-resource pair ('Returns a horse's career record') and enumerates the returned payload: starts, wins, top-three finishes, win percentage, plus past races with result lines. It is clearly a detail-by-id lookup, distinguishable from list-style siblings such as fanduel_racing_past_races or race-level fanduel_racing_race.

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?

It states the prerequisite explicitly — the id must come from the `search` route's runner result — and warns that an unknown id returns 404, which tells the agent to resolve the id first rather than guess. It stops short of naming competing tools (e.g. past_race vs past_races) to state exclusions, so it earns a 4 rather than a 5.

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