Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

fanduel_sportsbook_event_players

Fetch FanDuel Sportsbook event teams and player rosters by event ID, returning team names, abbreviations, colors, logos, jersey numbers, and positions for live event data.

Instructions

FanDuel Sportsbook event teams and player roster. Returns the teams (names, abbreviations, colors, logos) and player roster (name, team, jersey number, position) the live-data provider holds for an event.

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": {
      "event_id": "<event_id>"
    },
    "name": "fanduel_sportsbook_event_players"
  }
}

Input Schema

NameRequiredDescriptionDefault
event_idYesEvent id from any Sportsbook events listing

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations to declare safety or behavior, the description carries the full burden. It does add useful scope context ('the live-data provider holds for an event'), implying completeness is provider-dependent, but it says nothing about read-only nature, permissions, errors, or empty results.

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?

Two compact sentences that front-load the returned resource and then enumerate fields. No wasted clauses, though the opening is a noun phrase rather than a direct verb, making it slightly less immediately actionable.

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

Completeness3/5

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

With no output schema, the description usefully enumerates returned team and player fields and notes provider-held data. However, it omits any routing context versus similar FanDuel event/roster siblings and says nothing about result cardinality or request prerequisites, leaving gaps for a 1-parameter lookup tool.

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?

There is a single parameter with 100% schema description coverage ('Event id from any Sportsbook events listing'), so the schema already supplies its meaning. The description adds no further semantics or format guidance, making baseline 3 appropriate.

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 resource (event teams and player roster) and enumerates the returned fields (team names, abbreviations, colors, logos; player name, team, jersey number, position). It does not explicitly distinguish itself from close siblings such as fanduel_sportsbook_team_roster or fanduel_sportsbook_event_box_score, which is why it falls short of a 5.

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

Usage Guidelines2/5

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

The description says what the tool returns but never states when to use it, when not to, or which sibling to prefer (e.g., team_roster vs. event_box_score). The only usage hint, 'event id from any Sportsbook events listing,' lives in the schema, not the description.

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