Skip to main content
Glama

Get My Team (personalized snapshot)

fantasy_get_my_team
Read-onlyIdempotent

One call for YOUR team in ONE league: standing, current matchup and roster (with lineup locks) together. SINGLE-league only: for anything plural ("my teams", "how am I doing", "my week") use fantasy_get_my_teams.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "fantasy_get_my_team"
  }
}

Input Schema

NameRequiredDescriptionDefault
sportNoe.g. 'NFL', 'NBA'. Needed for ESPN/Sleeper and Fantrax name lookups.
seasonNoSeason year, e.g. 2025; ignored by Fantrax.
providerNoFantasy platform. Optional: defaults to your connected platform ('sleeper').
league_idNoOmit when connected. League id (Fantrax also takes the league URL).
team_queryNoYour team's exact id (preferred) or unique name; labels it (your team). Fantrax needs it (no owner data); ESPN/Sleeper auto-detect. Ids: fantasy_get_league_info.
credentialsNoOnly 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_queryNoA connected league's name/id; omit to auto-pick (primary first). Never ask for ids.
response_formatNo'markdown' (default, most compact) or 'json' (same normalized data, not the raw payload).markdown

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / provider / enum
      Previous value: -[
      -  "fantrax",
      -  "espn",
      -  "sleeper"
      -]New value: +[
      +  "fantrax",
      +  "espn",
      +  "sleeper",
      +  "yahoo"
      +]
  2. Changed2 schema fields changed
    • changedInput schema / properties / credentials / additionalProperties
      Previous value: -trueNew value: +{}
    • changedInput schema / properties / season / anyOf
      Previous value: -[
      -  {
      -    "type": "integer"
      -  },
      -  {
      -    "type": "string"
      -  }
      -]New value: +[
      +  {
      +    "maximum": 9007199254740991,
      +    "minimum": -9007199254740991,
      +    "type": "integer"
      +  },
      +  {
      +    "type": "string"
      +  }
      +]
  3. Changed7 schema fields changed
    • 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 / 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 / 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: -"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."New value: +"Your team's exact id (preferred) or unique name; labels it (your team). Fantrax needs it (no owner data); ESPN/Sleeper auto-detect. Ids: fantasy_get_league_info."
  4. 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"
      -]
  5. First observed

TDQS

A4.4/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, open-world), so the bar is lower. The description's real contribution is disclosing that this is an aggregating call returning standing + matchup + roster together, which tells the agent it need not chain fantasy_get_standings and fantasy_get_matchups; it does not discuss failure modes or partial-availability behavior.

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?

Two tightly constructed sentences: the payload and scope first, the routing rule second. No filler, no restatement of the title, and the constraint that matters most is front-loaded.

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?

With no output schema, the description still names the three returned sections and the lineup-lock detail, and it clarifies the single-league boundary for an 8-parameter tool whose params are fully documented. Minor gap: it does not characterize how the three sections are shaped in markdown vs json, though response_format's schema note partially covers it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and each parameter already carries a detailed description (provider defaults, credentials, team_query id preference), so the schema does the heavy lifting. The description only reinforces single-league scoping, adding nothing beyond the schema on individual parameters.

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+scope ('One call for YOUR team in ONE league') and enumerates the composite payload: standing, current matchup, roster with lineup locks. It is immediately distinguishable from fantasy_get_my_teams, which is named as the plural alternative.

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?

Explicitly partitions usage: single league here, and any plural phrasing ("my teams", "how am I doing", "my week") routes to fantasy_get_my_teams. Both the when and the when-not are stated with the alternative named.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources