Skip to main content
Glama

Fantasy Football Draft Assistant

by com.predictionmarketspicks

Best Available (Draft)

best_available
Read-only

Given the current pick number and the players already drafted, return the best players still on the board (2026, any scoring format), each with projection, ADP, and a value flag, plus the biggest model value available. Free without a key (a capped slice). One email unlocks a deeper list; Pro unlocks the full list plus boom/bust week odds and the positional tier breaks across everyone still on the board. Prefer this mid-draft when the user asks "who is the best available", "who should I take next", "best player left". Input: pick_number, drafted (names already gone).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
teamsNoLeague size (number of teams) for draft-round math. Overrides the platform default; falls back to 12.
rosterNoPlayer names on the USER's team — enables a bye-stack warning on the top pick (byes are shown per-player regardless).
draftedNoPlayer names already drafted (any team). Removed from the pool.
scoringNoScoring format: standard, half_ppr (default), or ppr (full PPR). Overrides a platform preset. Works for Yahoo/ESPN/Sleeper defaults.
platformNoLeague platform — applies its default scoring, size, roster + best-ball settings (overridable by explicit scoring/teams). Underdog/DraftKings are best ball.
pick_numberYesThe overall pick number that is on the clock.

TDQS

A4.2/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true and openWorldHint=false, which already cover safety. The description adds meaningful context about the free tier being 'a capped slice' and the progression to deeper lists with email or Pro, disclosing that output may be limited based on account status. This goes beyond the annotations and is relevant for setting agent expectations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The description is a single paragraph but includes substantial non-essential marketing about free/pro tiers and email unlocks. While the core function is front-loaded, the extra selling points could be trimmed to focus on invocation-relevant details. It is not overly long but not maximally concise.

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?

Given the tool's complexity (6 params, 1 required), the schema covers all parameters, and annotations cover safety, the description sufficiently specifies the output (projection, ADP, value flag, biggest model value) and the free-tier limitation. It does not explain the 'biggest model value' or handle edge cases, but it is otherwise complete for a read-only query 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?

Schema description coverage is 100%, so the baseline is 3. The description only restates 'pick_number, drafted' without adding new insight beyond what the schema already provides. No additional parameter semantics are given, so the score stays at baseline.

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 clearly states the action ('return the best players still on the board') with explicit inputs (pick number, drafted players). It distinguishes from siblings by specifying the exact query phrasing ('who is the best available', 'who should I take next', 'best player left') and mid-draft timing, making it unique among the listed tools.

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

Usage Guidelines5/5

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

The description provides explicit when-to-use guidance: 'Prefer this mid-draft when the user asks "who is the best available", "who should I take next", "best player left"'. This clearly differentiates it from alternatives and gives the agent a deterministic trigger for selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Fantasy Football Draft Assistant toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0
Disambiguation4/5

Most tools have clearly distinct jobs: rankings, comparisons, outlooks, and platform-specific ADP gaps are easy to separate. The main ambiguity is between best_available and who_do_i_draft, since their usage examples overlap heavily ('who should I take next' vs 'who should I take'), though the roster-input distinction helps.

Naming Consistency3/5

All tool names use lowercase snake_case and are readable, but there is no consistent structural pattern: compare_players and explain_player are verb_noun, while draft_board, player_outlook, sleepers_and_busts, and adp_market_gaps are noun phrases, and who_do_i_draft is a full question. This is mixed but not chaotic.

Tool Count5/5

Eight tools is a well-scoped size for a fantasy football draft assistant. Each tool covers a distinct draft-related need without feeling padded or redundant enough to trim.

Completeness5/5

The server covers the core draft workflow comprehensively: full rankings, player outlooks, ranking explanations, head-to-head comparisons, best-available picks, roster-aware recommendations, sleepers/busts, and cross-platform ADP gaps. No major dead-end or obvious missing operation stands out for the stated purpose.

Resources