Skip to main content
Glama

fanduel_sportsbook_team_roster

Read-only

Get a FanDuel Sportsbook team's roster with each player's roster status and injury designation (Q or O). Use injured_only for an injury report, or status and position filters; the response counts every status and position so valid values are visible. NFL and NBA only.

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>",
      "team": "<team>"
    },
    "name": "fanduel_sportsbook_team_roster"
  }
}

Input Schema

NameRequiredDescriptionDefault
teamYesTeam slug from fanduel_sportsbook_teams, such as arizona-cardinals.
leagueYesLeague: nfl or nba (the only leagues with rosters).
statusNoKeep only this roster status code, such as IR; valid codes are in the response statuses.
positionNoKeep only this position code, such as QB; valid codes are in the response positions.
injured_onlyNoReturn only players with an injury designation.

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

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds real behavioral context beyond that: the response carries roster status and injury designations (Q/O), and it returns counts of every status and position so agents can self-discover valid codes. This is meaningful disclosure about response shape, not repetition.

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?

Three tight sentences, front-loaded with the core action and resource. Every clause carries information (return contents, filter usage, valid-value discovery, league scope) with no filler or redundancy.

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

Completeness5/5

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

An output schema exists, so return-value explanation is not the description's burden, yet it still summarizes key fields. With annotations covering safety and the schema covering parameters, the description supplies everything needed (scope, filter intent, value discovery) to call the tool correctly.

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 all five parameters are already documented, setting a baseline of 3. The description adds value beyond the schema by explaining the intended use of injured_only ('for an injury report') and the discovery mechanism that reveals valid status/position codes, which a bare schema does not convey.

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 opens with a specific verb and resource ('Get a FanDuel Sportsbook team's roster') and states what each entry contains (roster status, injury designation). It scopes to 'NFL and NBA only,' making the tool's boundaries explicit. It stops short of naming how it differs from close siblings such as fanduel_sportsbook_team_depth_chart, but the core purpose is unambiguous.

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

Usage Guidelines4/5

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

It gives concrete usage direction: 'Use injured_only for an injury report, or status and position filters,' and explains how to discover valid filter values ('the response counts every status and position'). No explicit when-not-to-use or sibling routing is provided, but the filter guidance is actionable.

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.