DraftCall-MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| compare_playersA | Compare any two NFL players head to head for fantasy football: points per game in the requested scoring format, volume stats, bye weeks, and which one produced more. Use this for start/sit, draft, and trade questions about two specific players. |
| get_rankingsA | Fantasy football rankings for a position in a given scoring format, ordered by points per game. Positions: qb, rb, wr, te, flex, k, def. Use this for "who are the best X" and draft board questions. |
| get_playerA | A single player's fantasy profile: positional rank, points per game in all three scoring formats, season stats, games played, and bye week. |
| search_playersB | Find players by partial name, team abbreviation, or position. Use this when a name is ambiguous or only partly known before calling the other tools. |
| get_positional_scarcityA | How steep the fantasy dropoff is at each position in a given scoring format, measured from the top player to replacement level. Use this for draft-strategy questions like whether to take a running back or a wide receiver first. |
| get_bye_conflictsA | Given a list of players, report which bye weeks two or more of them share. Use this for roster planning and draft questions about stacking byes. |
| get_weekly_matchupA | Who a player faces in a given week of the 2026 season, whether it is home or away, and how generous that opponent has been to that position. Use this for in-season start or sit questions that name a week, which the season-long tools cannot answer. |
| verify_claimA | Check a number you are about to state, or one a user has stated, against DraftCall data for one player: points per game, games played, bye week, positional rank, or any season stat such as rushingYards or receptions. Returns whether the figure matches and the actual value when it does not. Use this before quoting a figure from memory, and whenever a user asserts a stat. |
| get_strength_of_scheduleA | How easy or hard a team's schedule is for one fantasy position, over the full season and over the fantasy playoff weeks (14 through 17), measured as the average fantasy points its opponents allowed to that position over the prior completed season. Give a team abbreviation or a player name; give only a position to rank all 32 teams. Use this for rest-of-season stash, trade deadline, and playoff planning questions. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| start_sit | Decide between two players for one lineup slot, for a given week and scoring format. |
| draft_pick | Choose between candidate players for a draft pick, using rankings, tiers, and positional scarcity. |
| bye_planning | Audit a roster for stacked bye weeks and name the weeks that need cover. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| methodology | Season basis, scoring formats, tiers, scarcity, opponent difficulty, and strength of schedule, in one page. |
TDQS
Scored across 9 tools
Each tool has a clearly distinct purpose: player profiles, head-to-head comparison, rankings, search, positional scarcity, bye-week conflicts, weekly matchups, strength of schedule, and stat verification. No two tools overlap in function; even the matchup-related tools (weekly vs. season-long) target different timeframes.
All tool names follow a consistent verb_noun pattern using snake_case: get_player, compare_players, get_rankings, search_players, get_positional_scarcity, get_bye_conflicts, get_weekly_matchup, get_strength_of_schedule, verify_claim. The verbs are descriptive and the pattern is uniform throughout.
With 9 tools, the server is well-scoped for a fantasy football data API. Each tool addresses a distinct query type, and the count feels neither bloated nor sparse—it covers the core needs of draft, start/sit, and trade analyses without redundancy.
The surface is remarkably complete for a read-only fantasy data service: it handles player identification (search), profiles, direct comparisons, rankings by position, draft strategy (scarcity), bye-week planning, weekly matchup context, season-long strength of schedule, and fact verification. No obvious dead ends or missing queries that would derail an agent.