League Loom

Get Fantasy Matchups

fantasy_get_matchups

Read-onlyIdempotent

Head-to-head scores for the current or a requested period, league-wide or for one team (team_query). THE source for live scoring and box-score recaps; season player data is not live scoring. For "who is scoring" or mid-game player updates, pass live=true and include_players=true. Returns league fantasy points, separate projections, available raw stats/game progress, retrieval time and provisional/final status; a refresh is a new snapshot, not continuous streaming. ESPN/Sleeper supply player points (raw stat categories NFL-only; Sleeper NFL adds projections from the league's scoring). Partial subtotals list missing categories and unsupported rules: never treat them as complete totals. Fantrax: team totals only, and scores need a publicly viewable league (others get pairings without scores); roto/points leagues have no matchups.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`live`	No	Fresh scores: ESPN live scoreboard; Sleeper current league points with NFL stats/game progress where available; Fantrax team totals with stated feed limits. A snapshot, not streaming.
`week`	No	Week/scoring period. Omit for current.
`sport`	No	e.g. 'NFL', 'NBA'. Needed for ESPN/Sleeper and Fantrax name lookups.
`season`	No	Season year, e.g. 2025; ignored by Fantrax.
`provider`	No	Fantasy platform. Optional: defaults to your connected platform ('sleeper').
`league_id`	No	Omit when connected. League id (Fantrax also takes the league URL).
`team_query`	No	One team's matchup. An exact name/id wins; an ambiguous name must be made more specific.
`credentials`	No	Only WITHOUT a connected profile: secret_id (Fantrax), espn_s2 + swid (private ESPN), username or user_id (Sleeper discovery). Public ESPN and Sleeper reads need none.
`league_query`	No	A connected league's name/id; omit to auto-pick (primary first). Never ask for ids.
`include_players`	No	Player scoring, starters/bench, game progress, and NFL player projections and stat categories (ESPN/Sleeper; Fantrax has team totals only). Pair with live=true mid-game.
`response_format`	No	'markdown' (default, most compact) or 'json' (same normalized data, not the raw payload).	markdown

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedSep 29, 2026

changedInput schema / properties / credentials / description

Previous value: -"Per-call credentials, only needed WITHOUT a connected profile. Keys: secret_id (Fantrax); espn_s2 + swid (private ESPN leagues); username or user_id (Sleeper discovery); session_cookie / auth_token + write_enabled:true (explicit write opt-in only). Public ESPN leagues and all Sleeper reads need none."New value: +"Only WITHOUT a connected profile: secret_id (Fantrax), espn_s2 + swid (private ESPN), username or user_id (Sleeper discovery). Public ESPN and Sleeper reads need none."

changedInput schema / properties / include_players / description

Previous value: -"Include player scoring, starters/bench, available game progress, and NFL player projections and stat categories. Use with live=true for mid-game updates. ESPN/Sleeper; Fantrax shows team totals."New value: +"Player scoring, starters/bench, game progress, and NFL player projections and stat categories (ESPN/Sleeper; Fantrax has team totals only). Pair with live=true mid-game."

changedInput schema / properties / league_id / description

Previous value: -"The platform's league id (Fantrax also accepts the full league URL)."New value: +"Omit when connected. League id (Fantrax also takes the league URL)."

changedInput schema / properties / league_query / description

Previous value: -"League name/id filter, for when the profile has several leagues on the provider."New value: +"A connected league's name/id; omit to auto-pick (primary first). Never ask for ids."

changedInput schema / properties / live / description

Previous value: -"Refresh scoring: ESPN live scoreboard; Sleeper current league points with available NFL stats/game progress; Fantrax team totals with explicit feed limits. This is a snapshot, not streaming."New value: +"Fresh scores: ESPN live scoreboard; Sleeper current league points with NFL stats/game progress where available; Fantrax team totals with stated feed limits. A snapshot, not streaming."

changedInput schema / properties / response_format / description

Previous value: -"'markdown' (default) or 'json' (raw payload)."New value: +"'markdown' (default, most compact) or 'json' (same normalized data, not the raw payload)."

changedInput schema / properties / season / description

Previous value: -"Season year, e.g. 2025. Required for ESPN/Sleeper league discovery; ignored by Fantrax."New value: +"Season year, e.g. 2025; ignored by Fantrax."

changedInput schema / properties / sport / description

Previous value: -"Sport, e.g. 'NFL', 'NBA', 'MLB', 'NHL'. Required for ESPN/Sleeper and Fantrax name lookups."New value: +"e.g. 'NFL', 'NBA'. Needed for ESPN/Sleeper and Fantrax name lookups."

changedInput schema / properties / team_query / description

Previous value: -"Optional: show one team’s matchup. Exact team name/id wins; ambiguous matches require a more specific name."New value: +"One team's matchup. An exact name/id wins; an ambiguous name must be made more specific."

changedInput schema / properties / week / description

Previous value: -"Week/scoring period. Omit for current week."New value: +"Week/scoring period. Omit for current."

Changed1 schema field changedSep 26, 2026

changedInput schema / properties / include_players / description

Previous value: -"Include player scoring, starters/bench, separate projections and available game progress/stat categories. Use with live=true for mid-game updates. ESPN/Sleeper; Fantrax shows team totals."New value: +"Include player scoring, starters/bench, available game progress, and NFL player projections and stat categories. Use with live=true for mid-game updates. ESPN/Sleeper; Fantrax shows team totals."

Changed3 schema fields changedSep 13, 2026

changedInput schema / properties / include_players / description

Previous value: -"Include per-player weekly box scores (ESPN/Sleeper; Fantrax shows team totals)."New value: +"Include player scoring, starters/bench, separate projections and available game progress/stat categories. Use with live=true for mid-game updates. ESPN/Sleeper; Fantrax shows team totals."

changedInput schema / properties / live / description

Previous value: -"ESPN only: live in-progress scoreboard."New value: +"Refresh scoring: ESPN live scoreboard; Sleeper current league points with available NFL stats/game progress; Fantrax team totals with explicit feed limits. This is a snapshot, not streaming."

addedInput schema / properties / team_query

Added value: +{
+  "description": "Optional: show one team’s matchup. Exact team name/id wins; ambiguous matches require a more specific name.",
+  "type": "string"
+}

Changed16 schema fields changedSep 10, 2026

changedInput schema / properties / credentials / additionalProperties
```
Previous value: -falseNew value: +true
```

changedInput schema / properties / credentials / description

Previous value: -"Per-call credentials. Fill only the keys your provider needs (see fantasy_list_providers). Public ESPN leagues and all Sleeper reads need none."New value: +"Per-call credentials, only needed WITHOUT a connected profile. Keys: secret_id (Fantrax); espn_s2 + swid (private ESPN leagues); username or user_id (Sleeper discovery); session_cookie / auth_token + write_enabled:true (explicit write opt-in only). Public ESPN leagues and all Sleeper reads need none."

removedInput schema / properties / credentials / properties / espn_s2

Removed value: -{
-  "description": "ESPN private-league cookie 'espn_s2' (DevTools → Application → Cookies → espn.com).",
-  "type": "string"
-}

removedInput schema / properties / credentials / properties / secret_id

Removed value: -{
-  "description": "Fantrax Secret ID (User Profile → 'Your Secret ID').",
-  "type": "string"
-}

removedInput schema / properties / credentials / properties / swid

Removed value: -{
-  "description": "ESPN private-league cookie 'SWID': a GUID in curly braces, e.g. {XXXX-...}.",
-  "type": "string"
-}

removedInput schema / properties / credentials / properties / user_id

Removed value: -{
-  "description": "Sleeper numeric user_id (alternative to username).",
-  "type": "string"
-}

removedInput schema / properties / credentials / properties / username

Removed value: -{
-  "description": "Sleeper username (for league discovery).",
-  "type": "string"
-}

changedInput schema / properties / include_players / description

Previous value: -"Include each team's per-player weekly box score (starters and bench with their fantasy points). ESPN and Sleeper only; Fantrax shows team totals. Off by default to keep matchup reads light."New value: +"Include per-player weekly box scores (ESPN/Sleeper; Fantrax shows team totals)."

changedInput schema / properties / league_id / description

Previous value: -"The league id from the platform. For Fantrax, a full league URL is also accepted and the server extracts the id."New value: +"The platform's league id (Fantrax also accepts the full league URL)."

changedInput schema / properties / league_query / description

Previous value: -"Optional profile league name/id filter. Use when the profile has multiple leagues for the provider."New value: +"League name/id filter, for when the profile has several leagues on the provider."

changedInput schema / properties / live / description

Previous value: -"ESPN only: use the live scoreboard view for in-progress scoring."New value: +"ESPN only: live in-progress scoreboard."

changedInput schema / properties / provider / description

Previous value: -"Fantasy platform: 'fantrax', 'espn', or 'sleeper'. Call fantasy_list_providers first to see each provider's capabilities and required credentials."New value: +"Fantasy platform. Optional: defaults to your connected platform ('sleeper')."

changedInput schema / properties / response_format / description

Previous value: -"Output format: 'markdown' (default, human-readable) or 'json' (raw upstream payload)."New value: +"'markdown' (default) or 'json' (raw payload)."

changedInput schema / properties / season / description

Previous value: -"Season year, e.g. 2024. REQUIRED for espn and sleeper league discovery; ignored by fantrax."New value: +"Season year, e.g. 2025. Required for ESPN/Sleeper league discovery; ignored by Fantrax."

changedInput schema / properties / sport / description

Previous value: -"Sport, e.g. 'NFL', 'NBA', 'MLB', 'NHL'. Required for ESPN/Sleeper and for Fantrax player/name lookups."New value: +"Sport, e.g. 'NFL', 'NBA', 'MLB', 'NHL'. Required for ESPN/Sleeper and Fantrax name lookups."

removedInput schema / required
```
Removed value: -[
-  "provider"
-]
```

First observedJun 29, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive), so the bar is lower, yet the description adds real behavioral context: a refresh is a new snapshot rather than streaming, partial subtotals list missing categories and must not be treated as complete, and private-league credentials are required for non-public reads. It stops short of describing pagination or how large league-wide snapshots behave, so it is not a full 5.

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?

Front-loads the core purpose and the live-scoring distinction in the first two sentences, then branches by provider. Dense and jargon-heavy ('raw stat categories NFL-only') but each clause carries load; slightly long for a single description.

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?

Covers an 11-parameter tool with a nested credentials object and no output schema: it describes the return payload (fantasy points, separate projections, raw stats/game progress, retrieval time, provisional/final status), provider-by-provider data availability, and auth requirements. Nothing an agent needs to call it correctly is missing.

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 description coverage is 100%, so the 3 baseline applies, but the description adds cross-parameter semantics the schema cannot: the live=true + include_players=true pairing for mid-game use, and the team_query interpretation of ambiguous names. It adds genuine conditional meaning beyond the per-field docs.

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?

States a specific verb+resource (head-to-head scores) and scope (league-wide or one team), then explicitly distinguishes itself from the sibling it could be confused with: 'season player data is not live scoring.' An agent can pick this over fantasy_get_player_data without opening either schema.

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?

Gives concrete when-to-use triggers ('who is scoring' or mid-game updates → live=true and include_players=true) and explicit boundaries for each provider (Fantrax team totals only; roto/points leagues have no matchups; scores require a publicly viewable league). Exclusions and alternatives are named rather than implied.

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

All League Loom tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?