Skip to main content
Glama

league-loom

by com.leagueloom
OverviewDiscussionsAdmin

Get Fantasy League Info

fantasy_get_league_info
Read-onlyIdempotent

A league's name, teams (with owners on ESPN/Sleeper), scoring, and key settings — also the source of team ids for team_query. Profile-first: the league is inferred when connected, so don't ask for ids.

"Your team" (⭐): ESPN/Sleeper auto-detect it; Fantrax exposes no owner data, so pass team_query. Fantrax league_id may be the full league URL.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sportNoSport, e.g. 'NFL', 'NBA', 'MLB', 'NHL'. Required for ESPN/Sleeper and Fantrax name lookups.
seasonNoSeason year, e.g. 2025. Required for ESPN/Sleeper league discovery; ignored by Fantrax.
providerNoFantasy platform. Optional: defaults to your connected platform ('sleeper').
league_idNoThe platform's league id (Fantrax also accepts the full league URL).
team_queryNoYour 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.
credentialsNoPer-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_queryNoLeague name/id filter, for when the profile has several leagues on the provider.
response_formatNo'markdown' (default) or 'json' (raw payload).markdown

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed15 schema fields changed
    • 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"
-]
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already mark the tool as read-only, idempotent, and non-destructive. The description adds meaningful behavioral detail beyond that, including platform-specific behavior for Fantrax (no owner data, full league URL accepted) and ESPN/Sleeper auto-detection of the user's team. This helps set expectations without contradicting the 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 dense but front-loaded, with the core purpose stated first and platform details in a secondary paragraph. Some points repeat the schema's parameter descriptions, but the overall structure is efficient and scannable.

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?

For a tool with 8 parameters and no output schema, the description covers the essential behavioral context: what the tool returns, when to avoid passing ids, how Fantrax differs, and how to mark the user's team. It is complete enough for an agent to invoke the tool correctly, though it does not explain the response envelope.

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?

The input schema covers all 8 parameters with descriptions, so the baseline is 3. The tool description adds extra meaning by clarifying team_query's role in marking the starred team, the Fantrax league_id URL possibility, and the profile-first inference model. This goes beyond simply restating the 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 clearly states the tool returns a league's name, teams, scoring, and key settings, and highlights that it is the source of team ids for team_query. This distinguishes it from sibling tools like fantasy_get_league_health or fantasy_get_standings, making the purpose specific and actionable.

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?

The description gives practical guidance: the league is inferred when a profile is connected so users should not ask for ids, and Fantrax requires team_query because it exposes no owner data. It does not explicitly name alternative tools or say when not to use this tool, but the context is clear and useful.

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

All league-loom toolsInspect
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