Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fanduel_sportsbook_teams

Lists a league's teams grouped by conference or division with ATS, moneyline, and over/under records, colors, coaches, and next games; returned slugs feed team routes.

Instructions

FanDuel Sportsbook team index. Lists a league's teams grouped by conference or division, each with its season record against the spread, on the money line and on the over/under, its colors, head coach where published, and its next game. sections lists the team pages the league has (all six for the NFL; odds and news only for MLB and the college leagues). Team slug values feed the other team routes.

Input Schema

NameRequiredDescriptionDefault
leagueNoLeague: `nfl` (default), `nba`, `mlb`, `college-football`, `college-basketball`

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does it well: it discloses the payload contents (spread/ML/over-under records, colors, head coach 'where published', next game) and caveats coverage by league (six sections for NFL versus only odds and news for MLB and college leagues). Undisclosed are pagination, error behavior, or freshness of records.

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?

Three tight sentences, front-loaded with the resource and its contents, then the league caveat, then the slug hand-off. Dense but efficient; the `sections` sentence is slightly cryptic since that concept is never defined.

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 no output schema, the description must describe return values, and it enumerates them thoroughly plus the league-dependent variance. Only freshness, pagination and volume of teams are left unstated — minor for a read-only index with a single optional parameter.

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 league enum and default are already documented. The description goes beyond the schema by explaining that the value changes what `sections` contains — a real semantic consequence of the parameter choice.

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 and resource — 'FanDuel Sportsbook team index. Lists a league's teams grouped by conference or division' — and names the fields returned. It positions itself as the index whose slugs feed the other team routes, which distinguishes it from the prefixed team_* siblings, though it never names them directly.

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 only implied: this is where you enumerate a league's teams and obtain slugs for downstream team calls. There is no explicit 'use this instead of X' or when-not guidance against dozens of overlapping fanduel_sportsbook_* team 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