Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fanduel_sportsbook_player_stats

Get career and per-season player statistics for NFL and NBA players from FanDuel Sportsbook data, including regular-season, playoff, and preseason splits.

Instructions

FanDuel Sportsbook player statistics. Returns a player's career and per-season statistics. The groups differ by sport (NFL: career rows plus regular-season and post-season weeks; NBA: regular-season and playoff careers plus preseason, regular-season and play-in seasons) and are passed through with snake_case keys. Available for NFL and NBA players.

Input Schema

NameRequiredDescriptionDefault
leagueYesLeague: `nfl`, `nba`
playerYesPlayer slug ending in its id, such as `josh-allen-53775`; take it from the `players` route (`players[].slug`) or `team/roster` (`players[].slug`)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations and no output schema, the description carries the full disclosure burden and does it well: it explains the returned group structure per sport (career rows, regular-season weeks, post-season weeks for NFL; preseason/regular-season/play-in/playoff for NBA) and that keys are snake_case. It omits any mention of error behavior for unsupported leagues, empty-stat handling, or response size.

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?

Four sentences, front-loaded with the identification sentence and then the payload shape; each sentence carries distinct information. The parenthetical sport breakdown is dense but earns its space since there is no output schema to document those groups.

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?

Given no output schema and no annotations, the description supplies the one thing the agent most needs: the shape and grouping key differences of the returned statistics per league. It is complete enough to call correctly, with only secondary gaps (field-level contents, unsupported-league errors) remaining.

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 earns a bump by explaining the consequence of the `league` enum: the returned grouping differs materially between NFL and NBA. It adds no information about the `player` slug beyond what the schema already documents.

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 resource (FanDuel Sportsbook player statistics) and scopes it to career plus per-season data with the sport-specific group breakdown, so the agent knows exactly what it returns. It does not explicitly contrast with the near-siblings fanduel_sportsbook_stats, fanduel_sportsbook_team_stats, or fanduel_sportsbook_player_props, so an agent must infer the distinction from the parameters.

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

Usage Guidelines2/5

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

The description is purely descriptive of the payload. It never says when to reach for this versus fanduel_sportsbook_player (profile), fanduel_sportsbook_player_props, or fanduel_sportsbook_stats, nor does it name an alternative. The only usage-like signal is the closing 'Available for NFL and NBA players', which constrains but does not route.

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