league-loom

Get Fantasy Team Rosters

fantasy_get_rosters

Read-onlyIdempotent

Every team's roster with player names, positions, and slot/status; team_query filters to ONE team and marks it ⭐ ("my roster"). Profile-first: league and team inferred when connected.

ESPN/Sleeper auto-detect your team and resolve names; Fantrax needs sport (name resolution) and team_query (no owner data). For your roster + standing + matchup in one call, fantasy_get_my_team.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`sport`	No	Sport, e.g. 'NFL', 'NBA', 'MLB', 'NHL'. Required for ESPN/Sleeper and Fantrax name lookups.
`period`	No	Scoring/lineup period or week. Omit for current.
`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.
`response_format`	No	'markdown' (default) or 'json' (raw payload).	markdown

Schema Changelog

Changes observed during successful MCP inspections.

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

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

First observedJun 29, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds valuable behavioral context: provider differences (Fantrax lacks owner data), the star marking for the queried team, and credential nuances for private leagues. It does not contradict annotations.

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 well-structured: front-loaded with the core purpose, then provider-specific guidance, and ends with a pointer to an alternative. It uses semicolons for compactness and avoids redundancy. Slightly long but each sentence adds value.

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 (9 parameters, multiple providers, no output schema), the description covers essential behaviors: provider differences, credential requirements, and the star-marking behavior. It could mention what happens when no profile is connected, but the credentials parameter covers that. Overall sufficient 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 parameters are already documented. The description adds meaning beyond the schema, particularly for team_query (marks ⭐, required on Fantrax, auto-detected elsewhere) and provider-specific behavior for sport and season. This extra context helps agents choose and fill parameters correctly.

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's purpose: retrieving every team's roster with player names, positions, and slot/status, and notes the team_query filter for a single team. It distinguishes from siblings like fantasy_get_my_team and fantasy_get_my_players by scope (all teams vs. own team) and content (roster vs. players).

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 explicitly explains when to use this tool versus alternatives, including provider-specific requirements (Fantrax needs sport and team_query, ESPN/Sleeper auto-detect) and a pointer to fantasy_get_my_team for a combined roster+standing+matchup call. This is actionable guidance.

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?