Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fanduel_sportsbook_standings

Retrieve FanDuel Sportsbook standings for NFL, NBA, MLB, and college football, including team records, rankings, games back, and streak data in structured rows.

Instructions

FanDuel Sportsbook league standings. Returns a league's standings, one row per team with the team's identity and the record groups the Sportsbook shows for that league: conference, division and league rankings with home, road and streak records (NFL and NBA), games back, last ten and home and away records (MLB), or conference record, points and AP ranking (college football). Available for the NFL, NBA, MLB and college football.

Input Schema

NameRequiredDescriptionDefault
leagueYesLeague: `nfl`, `nba`, `mlb`, `college-football`

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does a solid job: it discloses that output is one row per team and that the record groups vary by league (NFL/NBA vs MLB vs college football). It omits anything about data freshness, season scoping, or error behavior for out-of-season leagues.

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?

Front-loaded with the core action and then the return shape; two sentences, dense but readable. The final sentence duplicates the schema enum, which is the one piece that does not earn its place.

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?

There is no output schema, so the description must describe return values, and it does so in useful per-league detail. It stops short of covering season/period scope or what happens for a league with no active standings, which is the remaining gap.

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?

Only one parameter, and the schema already documents the league enum at 100% coverage. The description's 'Available for the NFL, NBA, MLB and college football' merely re-lists the enum values without adding format or behavior meaning, so the baseline 3 applies.

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 and resource ('Returns a league's standings, one row per team') and identifies the source (FanDuel Sportsbook), which separates it from the many other standings tools. The per-league record-group detail further pins down exactly what this tool produces.

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 obvious standings purpose and the supported-league list, but there is no explicit when-to-use routing against alternatives such as espn_standings, yahoo_sports_standings, sofascore_standings or mlb_standings, all of which overlap. The 'Available for...' sentence restates the enum rather than guiding selection.

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