Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fanduel_racing_carryover_pools

List FanDuel Racing multi-race carryover pools with amounts, tracks, payout races, minutes to post, and status, sorted by pool amount; filter by track or race status.

Instructions

FanDuel Racing carry-over pools. Lists the multi-race pools that carried over (Pick 3 to Pick 6, Super High Five, Superfecta, Daily Double) with the amount, the track, the race the pool pays on and that race's minutes to post and status. Largest pool first. status filters by the status of the race the pool pays on.

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, from 1; default 1, at most 10000
limitNoItems per page, 1 to 200; default 50
trackNoKeep only these track codes (repeat the parameter or comma-separate), such as `LRL`; list codes with the `tracks` route
statusNoKeep only pools whose race has these statuses (repeat the parameter or comma-separate): `O` Open, `IC` Up Next, `SK` Race Off, `RO` Race Official

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A3.7/5.0
Behavior3/5

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

No annotations, so the description carries the full behavioral burden. It usefully discloses the sort order (largest pool first) and that status filters on the underlying race, but does not mention return format, pagination limits, or any auth/rate constraints a caller might need.

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?

Three tightly packed sentences, front-loaded with the resource definition before the fields and the status filter. Little waste, though the field enumeration is dense.

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 non-destructive, four-parameter filtered list with full schema coverage and no output schema, the description is nearly complete: purpose, returned fields, ordering, and filter semantics are all covered. Minor gap is lack of any usage/alternative routing.

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% with all four parameters documented, so the schema does the heavy lifting. The description's note that status filters by the race the pool pays on is mildly additive but largely restates the enum description already in the schema.

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 (Lists) and resource (multi-race carry-over pools), enumerates the pool types (Pick 3 to Pick 6, Super High Five, etc.), and names the fields returned with ordering. An agent can distinguish this from sibling racing tools like fanduel_racing_past_races or fanduel_racing_results without opening a schema.

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

Usage Guidelines3/5

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

The description makes the tool's scope clear and explains the status filter, but gives no explicit when-to-use versus alternatives or when-not guidance. Usage is implied by the resource definition rather than stated.

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