Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fanduel_sportsbook_team_stats

Retrieve a team's FanDuel Sportsbook season statistics for NFL or NBA, including sport-specific scoring, offense, defense, totals, and averages.

Instructions

FanDuel Sportsbook team statistics. Returns a team's season statistics. The groups differ by sport (scoring, offense, defense and special teams for the NFL; totals and averages for the NBA), so stats is an object with snake_case keys. Available for the NFL and NBA only.

Input Schema

NameRequiredDescriptionDefault
teamYesTeam slug from the `teams` route (`groups[].teams[].slug`), such as `arizona-cardinals`
leagueYesLeague: `nfl`, `nba`, `mlb`, `college-football`, `college-basketball`

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?

With no annotations, the description carries the disclosure burden and does meaningful work: it describes the return shape (`stats` is an object with snake_case keys) and warns that the stat groups vary by sport (scoring/offense/defense/special teams for NFL vs totals/averages for NBA). It omits error behaviour when an unsupported league is passed, which is the notable remaining gap.

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?

Four short, front-loaded sentences with no filler: purpose first, then the return shape, then the varying groups, then the coverage caveat. Each sentence carries distinct information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Because there is no output schema, the description's explanation of the `stats` object and per-sport grouping is genuinely necessary and partly supplied. But the conflict between 'NFL and NBA only' and a five-league enum is left unresolved, so an agent cannot tell which is authoritative before calling.

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%, so the enum values and slug format are already documented in the parameters; the description only restates league availability. Worse, it says NFL and NBA only while the schema enum lists mlb, college-football and college-basketball, so it adds ambiguity rather than clarity for `league`.

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+resource combination: returns a team's season statistics from FanDuel Sportsbook. It implicitly differentiates itself from siblings like team_odds, team_roster and team_depth_chart by scoping to 'season statistics', but it never names an alternative, so an agent must infer the boundary.

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?

Offers one real usage constraint — 'Available for the NFL and NBA only' — which tells the agent when the call is viable. However, it names no alternatives for the other leagues and gives no preconditions such as needing a team slug from the `teams` route (that lives only in the schema).

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