fantasy-mcp

Overview Schema Source Related Servers Discussions Admin

Get Free Agents

get_free_agents

Find free agents and waiver claims in your fantasy league. Filter by position, sort by ownership or projections to identify players to pick up.

Instructions

List available players (free agents and waiver claims) in the user's league.

Use this for "who should I pick up?", "best available RB", or "who's trending".

Args: position -- one of QB, RB, WR, TE, K, D_ST (case-insensitive; D/ST also accepted); omit for all positions. limit -- 1 to 50, default 10. sort -- "owned" (most rostered across ESPN first, default) or "projected" (highest season projection first).

Each player row: player_id (pass to get_player), name, position, pro_team, injury_status, status (FREEAGENT = add immediately; WAIVERS = must submit a claim), percent_owned (% of ESPN leagues rostering them), percent_change (ownership trend -- positive means being picked up), season_projected / season_points (full-season projected / scored so far), week_projected / week_points (current NFL week; 0.0 may mean not played yet OR played and scored nothing), and positional_rank (ESPN's season rank at their position; null if unavailable). Next-week projections are not available from this tool.

Input Schema

TableJSON Schema

Name	Required	Default
`sort`	No	owned
`limit`	No
`position`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Sep 14, 2026

TDQS

A4.8/5.0

Behavior5/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 so thoroughly: it explains status values (FREEAGENT vs WAIVERS), ownership trend interpretation, the ambiguity of 0.0 week points, and explicitly notes next-week projections are unavailable. This goes well beyond a basic list description.

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

Conciseness5/5

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

The description is long but every section earns its place: purpose and usage are front-loaded, args are compact, and the row-field explanation adds semantic nuance. No filler or repetition.

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 three-optional-parameter list tool with no annotations, the description covers what the tool does, when to use it, all parameter semantics, and the meaning of every returned field. Nothing needed to invoke or interpret results is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, but the description fully documents all three parameters: position values including aliases and case-insensitivity, limit range and default, and sort options with their meanings. It compensates completely for the bare schema.

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 opens with 'List available players (free agents and waiver claims) in the user's league', a specific verb and resource that clearly distinguishes it from sibling tools like get_my_team or get_player. The scope ('available', 'free agents and waiver claims') makes its purpose unambiguous.

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

Usage Guidelines4/5

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

It gives explicit use cases: 'who should I pick up?', 'best available RB', or 'who's trending'. It does not explicitly state when to prefer a sibling tool, though the output row directs passing player_id to get_player, providing a mild routing hint.

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

Deploy Server