league-loom

Get Fantasy Matchups

fantasy_get_matchups

Read-onlyIdempotent

Current head-to-head scoring or a requested matchup period. Use team_query to limit detail to one team’s matchup. For "how am I doing right now", "who is scoring" or mid-game player updates, use live=true and include_players=true. Returns league fantasy points, separate projections, available raw stats/game progress, retrieval time and provisional/final status. ESPN/Sleeper supply player points; detailed raw stats vary by sport and source. A refresh is a new snapshot, not continuous streaming. This is THE source for live scoring and box-score recaps; season player data is not live scoring. Profile-first: league inferred when connected.

Fantrax: public/viewable leagues only, team totals only; roto/points leagues have no matchups.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`live`	No	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.
`week`	No	Week/scoring period. Omit for current week.
`sport`	No	Sport, e.g. 'NFL', 'NBA', 'MLB', 'NHL'. Required for ESPN/Sleeper and Fantrax name lookups.
`season`	No	Season year, e.g. 2025. Required for ESPN/Sleeper league discovery; ignored by Fantrax.
`provider`	No	Fantasy platform. Optional: defaults to your connected platform ('sleeper').
`league_id`	No	The platform's league id (Fantrax also accepts the full league URL).
`team_query`	No	Optional: show one team’s matchup. Exact team name/id wins; ambiguous matches require a more specific name.
`credentials`	No	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.
`league_query`	No	League name/id filter, for when the profile has several leagues on the provider.
`include_players`	No	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.
`response_format`	No	'markdown' (default) or 'json' (raw payload).	markdown

Schema Changelog

Changes observed during successful MCP inspections.

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.7/5.0

Behavior5/5

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

Annotations already cover read-only, idempotent, open-world, and non-destructive safety. The description adds substantial behavioral context beyond that: return contents (league points, projections, raw stats/game progress, retrieval time, provisional/final status), provider variability, snapshot-vs-streaming behavior, and Fantrax restrictions.

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 dense but front-loaded: purpose first, then usage conditions, return shape, provider caveats, and Fantrax limits. Every sentence contributes operational information, with no filler. The length is justified by the tool's 11-param complexity.

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?

With no output schema, the description steps in to explain what is returned, including points, projections, raw stats, game progress, retrieval time, and status. It also covers provider-specific behavior, auth/profile assumptions, and Fantrax limitations. Given the rich schema and annotations, nothing essential is missing for correct invocation.

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 schema already documents all 11 parameters thoroughly. The description adds practical meaning for team_query and the live/include_players combination, but it does not add equally useful semantics for every parameter. This exceeds the baseline 3 but is not a full parameter reference.

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 a specific verb and resource: current head-to-head scoring or a requested matchup period. It distinguishes this tool from season-level player data by stating 'season player data is not live scoring.' An agent can identify it as the live/box-score matchup tool without ambiguity.

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 clear usage contexts ('how am I doing right now', 'who is scoring', mid-game updates) and parameter guidance (live=true, include_players=true). It also provides an explicit exclusion for season player data and provider limitations for Fantrax. However, it does not name a sibling tool to use instead for season player data, which keeps it from full routing clarity.

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?