Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fanduel_research_nfl_schedule

Retrieve one NFL week's games with kickoff time, stadium, weather, TV, odds, team records, win probabilities, rankings and leaders by season phase and week.

Instructions

FanDuel Research NFL schedule. Returns one week of NFL games with kickoff time, stadium and roof type, weather, TV network, closing spread and total, status and game clock, and for each team its record, win probability, rankings, average yards, the game's box totals and its passing, rushing and receiving leaders. Games that have not finished also carry the Sportsbook event id, link and the money line, spread and total with the market and selection ids. season_type is PRE, REGULAR or POST; week is 0 to 4 for PRE, 1 to 18 for REGULAR and 1 to 5 for POST. A week with no games returns an empty list.

Input Schema

NameRequiredDescriptionDefault
weekYesWeek number; `0` to `4` for PRE (`0` is the Hall of Fame game), `1` to `18` for REGULAR, `1` to `5` for POST
season_typeNoSeason phase; default `REGULAR`

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A3.7/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden, and it does substantial work: it enumerates returned fields, discloses that unfinished games additionally carry sportsbook event id, link, money line, spread/total and market/selection ids, and warns that empty weeks return an empty list. It leaves unstated whether this is archived or live data, and any performance/rate characteristics, which is why it is not 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?

Purpose and scope are front-loaded in the first clause, and the lengthy field enumeration is justified because there is no output schema. The middle sentence is a heavily comma-loaded run-on that would scan better as a list, but no sentence is pure padding.

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?

With two well-documented parameters and no output schema, the description must explain returns, which it does comprehensively, including conditional fields for in-progress games and the empty-result case. Minor omissions (data freshness, auth requirements) keep it from being complete at a 5.

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 description coverage is 100%, so the baseline is 3. The description's season_type and week range text is essentially a verbatim restatement of the schema descriptions (including the Hall of Fame game note) rather than added semantics, and the default of REGULAR is only in the schema.

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: 'Returns one week of NFL games' from FanDuel Research, with an enumerated set of fields. An agent can tell what it returns without opening the schema. However it never names or distinguishes itself from look-alike siblings such as fanduel_sportsbook_schedule or yahoo_sports_team_schedule.

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?

Usage is implied by the precise scope (one week per season phase) but the description gives no explicit when-to-use/when-not guidance and names no alternative tool. The note that 'a week with no games returns an empty list' helps the agent interpret results but is not routing guidance.

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