Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fanduel_sportsbook_players

Search FanDuel Sportsbook NFL and NBA player directories by name to retrieve player slugs, IDs, and names, with pagination for paging through matches.

Instructions

FanDuel Sportsbook player directory. Searches the players that have Sportsbook player pages: about 2,400 in the NFL and 480 in the NBA. Each entry has the slug that the player routes take, the numeric player_id and a name spelled from the slug (without punctuation or accents; team/roster has the exact spelling). q matches every word against the slug, results are in slug order, and total counts all matches so limit and offset can page through them.

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`, `nba`
offsetNoPlayers to skip; default 0

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does well: it discloses dataset size, returned fields (`slug`, `player_id`, `name`), name spelling caveats, `q` word-matching semantics, result ordering, and pagination behavior. It does not explicitly discuss permissions or rate limits, but those are less central for a read-only directory search.

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?

The description is front-loaded and dense with useful information, with no obvious filler. It is slightly long in a single paragraph, but each sentence adds practical search or pagination context.

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?

For a 4-parameter search tool with no output schema and no annotations, the description is complete enough to call correctly: it explains the resource, result fields, matching behavior, ordering, and pagination. An agent has what it needs to search and page through player records.

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 the baseline is 3, but the description adds useful meaning by explaining that `q` matches every word against the slug and that `total` counts all matches for `limit`/`offset` paging. It also clarifies why the returned `name` may differ from exact roster spelling.

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?

The description states a specific verb and resource: it searches a FanDuel Sportsbook player directory, with clear scope by league and page coverage. It distinguishes itself from a detail lookup by framing the tool as a directory/search over players with Sportsbook pages.

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 through the `q` matching behavior, slug ordering, and pagination via `total`, and it hints that `team/roster` has exact spelling. However, it does not explicitly say when to use this tool versus `fanduel_sportsbook_player` or other sibling player tools.

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