Skip to main content
Glama

fanduel_sportsbook_standings

Read-only

Get a FanDuel Sportsbook league's standings: every team with its conference, division and league rankings and home, road and streak records (NFL, NBA), games back and last ten (MLB), or conference record and AP ranking (college football). Use it to rank teams; it needs league nfl, nba, mlb or college-football.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "league": "<league>"
    },
    "name": "fanduel_sportsbook_standings"
  }
}

Input Schema

NameRequiredDescriptionDefault
leagueYesLeague: nfl, nba, mlb or college-football.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds per-sport field variance (games back/last ten for MLB, AP ranking for college football), which is real behavioral context beyond annotations, but it largely restates return shape that the output schema already carries.

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 resource, then a compact clause on field variance per sport, then a usage note. Dense but every clause carries information; nothing is 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 one schema-covered parameter, an output schema, and safety annotations, the description covers what the tool returns per league and when to reach for it. Complete enough to call correctly; only sibling differentiation is 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 coverage is 100% and the single league parameter is documented in the schema. The description repeats the allowed values (nfl, nba, mlb, college-football) without adding syntax or meaning beyond the schema, so the baseline of 3 applies.

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 (Get) and resource (standings) scoped to FanDuel Sportsbook leagues, and clearly enumerates the returned fields for each supported league. It does not explicitly differentiate itself from the many sibling standings tools (espn_standings, mlb_standings, sofascore_standings), so the sibling-discrimination criterion is only partially met.

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?

"Use it to rank teams" gives a use case, and the description names the allowed league values. But it never contrasts with alternative standings tools or states when NOT to use it, leaving the agent to infer selection among many sibling standings endpoints.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.