Skip to main content
Glama

fanduel_sportsbook_players

Read-only

Search the FanDuel Sportsbook player directory, about 2,400 NFL and 480 NBA players, for the slug that the player tools take. Use it to find a player by name with q, paging with limit and offset; it needs league nfl or nba, and the name is spelled from the slug while fanduel_sportsbook_team_roster has the exact spelling.

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_players"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoWords to find in the player name, such as josh allen; omit to list everyone.
limitNoPlayers per page, 1 to 200; default 50.
leagueYesLeague: nfl or nba.
offsetNoPlayers to skip; default 0.

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 and openWorldHint, so the safety profile is covered; the description adds genuinely new context: directory size (~2,400 NFL, ~480 NBA), the paging model, and the fact that display name is reconstructed from the slug. It omits match semantics for q (substring vs exact word) and any result-order or truncation behavior, which is the main 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence, front-loaded with purpose before parameter details, with every clause carrying information. It is dense and somewhat run-on (purpose, lookup, paging, required param, and sibling caveat in one breath), which costs a point on readability but not on waste.

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 values need not be explained, and the description covers the full call chain: how to find a player, what the required league constraint is, how to page, and where to go for exact name spelling. Nothing critical to correct invocation 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 description coverage is 100%, so the schema already documents q, limit, offset and league; the description mostly restates them. The one piece of added meaning is the slug/name derivation relationship and the requiredness of league, but no new syntax, matching rules, or valid-value nuance is introduced. Baseline 3 is appropriate.

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 ('Search the FanDuel Sportsbook player directory') and immediately states the purpose of the output ('for the slug that the player tools take'). It explicitly contrasts with the sibling fanduel_sportsbook_team_roster, so an agent can tell the two apart without opening a schema.

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?

Gives a clear use case ('find a player by name with q') and names the alternative for exact name spelling (team_roster), which is real routing guidance. It stops short of saying when not to call it, e.g. if the caller already holds a slug from another source, and doesn't mention what happens when q matches mulitple players.

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.