Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fanduel_sportsbook_player

Retrieve an NFL or NBA player's overview page with name, team, season, recent news, and league-specific stats like season totals, game logs, or projections.

Instructions

FanDuel Sportsbook player overview. Returns a player's overview page: name, position, team, the season, and recent news with the player's updates. NFL players also carry season_totals and a game_log; NBA players carry stats (career and per-season lines) and projections. Available for NFL and NBA players; an unknown player id, or a player newly added to a roster whose page is still empty, returns 404.

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.8/5.0
Behavior4/5

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

There are no annotations, so the description carries the behavioral burden, and it does disclose the return contents and league-dependent field differences (`season_totals`/`game_log` for NFL, `stats`/`projections` for NBA). It also states the 404 behavior for unknown or newly added players with empty pages, though it does not mention authentication or rate limits.

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?

The description is front-loaded with the tool's purpose, then efficiently adds return fields, league-specific variations, and the 404 condition. Every sentence contributes actionable information without repetition or filler.

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 no output schema and no annotations, the description does a good job of explaining the response contents and the league-specific differences. It covers the important edge case of a 404 for unknown or empty player pages, though it could be slightly more explicit about the overall response shape or whether fields may be 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 description coverage is 100%, so both parameters are already documented with useful detail, including the `league` enum and the `player` slug format with example and source routes. The description adds only the high-level availability constraint for NFL/NBA and the 404 note, so the schema remains the primary source of parameter meaning.

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?

The description states a specific resource and action: it returns a FanDuel Sportsbook player's overview page, including name, position, team, season, news, and league-specific stats fields. This is clear enough to distinguish it from a generic player list, but it does not explicitly contrast it with sibling detail tools such as `fanduel_sportsbook_player_stats`, `fanduel_sportsbook_player_news`, or `fanduel_sportsbook_player_props`.

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 gives useful availability constraints: it works for NFL and NBA players, and unknown or empty player pages return 404. However, it does not say when an agent should choose this overview tool versus the dedicated player stats, player news, or player props siblings, leaving the main routing decision implicit.

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