league-loom

Get Schedule, Strength of Schedule, and Playoff Picture

fantasy_get_schedule

Read-onlyIdempotent

Full-season schedule, opponent strength-of-schedule, and a DETERMINISTIC playoff picture (seeds, clinched/eliminated, magic numbers — exact win/loss arithmetic, not simulation, so report clinches as guarantees). Use for "am I making the playoffs", "who's clinched", "who has the easier schedule", "rest-of-season outlook"; view picks a section. Profile-first: league inferred when connected.

ESPN/Sleeper full (Sleeper a touch slower); Fantrax: H2H schedule + partial SoS for public leagues, no clinch math.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`view`	No	Sections to return: 'all', game list only, strength of schedule only, or playoff picture only.	all
`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	Your team's exact id (preferred) or a unique name fragment; marks it ⭐. Required on Fantrax (no owner data there); ESPN/Sleeper auto-detect. Team ids come from fantasy_get_league_info.
`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_games`	No	Include the per-week game list.
`response_format`	No	'markdown' (default) or 'json' (raw payload).	markdown

Schema Changelog

Changes observed during successful MCP inspections.

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

changedInput schema / properties / team_query / description

Previous value: -"Identifies your team and marks it ⭐. Use the exact team id (preferred because it never breaks on rename) or a unique part of the team name. REQUIRED for Fantrax to identify your team: Fantrax exposes no owner data, so it cannot be auto-detected (ESPN/Sleeper auto-detect from your credentials). Get team ids from fantasy_get_league_info. For rosters this also filters to that team."New value: +"Your team's exact id (preferred) or a unique name fragment; marks it ⭐. Required on Fantrax (no owner data there); ESPN/Sleeper auto-detect. Team ids come from fantasy_get_league_info."

changedInput schema / properties / view / description

Previous value: -"Which sections to return: full ('all'), just the game list, just strength of schedule, or just the playoff picture."New value: +"Sections to return: 'all', game list only, strength of schedule only, or playoff picture only."

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

First observedJun 29, 2026

TDQS

A4.8/5.0

Behavior5/5

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

The description adds key behavioral context beyond annotations: determinism (clinches are guarantees, not simulations), provider differences (Fantrax partial features), and speed notes (Sleeper slower). This complements the readOnlyHint and idempotentHint without contradiction.

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?

The description is dense but each sentence contributes: core function, use cases, view selection, provider differences. It is structured with a colon and semicolon to separate ideas, though slightly long. It front-loads the purpose and essential usage before details.

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?

Given 10 parameters, multiple providers, and no output schema, the description covers what is returned (schedule, SOS, playoff picture), how to navigate sections via view, provider limitations, and credential needs. It is sufficiently complete for an agent to call correctly.

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 coverage is 100%, so the baseline is 3, but the description enriches parameters: view is explained with examples, team_query notes Fantrax requirement and source from fantasy_get_league_info, and credentials details are clarified. It adds meaningful guidance beyond schema text.

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 tool returns schedule, strength of schedule, and a deterministic playoff picture with exact arithmetic. It gives concrete use cases and specifies the resource, distinguishing it from sibling tools like matchups or standings.

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?

It explicitly lists when to use this tool ('am I making the playoffs', 'who's clinched', etc.) and notes the view parameter to pick a section. It also mentions provider-specific behaviors and profile-first league inference, giving clear context for selection.

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?