Skip to main content
Glama

league-loom

by com.leagueloom
OverviewDiscussionsAdmin

Get Recent League Transactions

fantasy_get_transactions
Read-onlyIdempotent

Recent league moves: adds, drops, waiver claims, and trades, newest first ("did my waiver claim process?", "what trades happened?"). Profile-first: league inferred when connected.

Sleeper: per-week with FAAB bids. ESPN: activity feed (trade legs may be partial). Fantrax: public/viewable leagues only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
weekNoWeek/scoring period (Sleeper defaults to current).
limitNoMax transactions, newest first (1-100).
sportNoSport, e.g. 'NFL', 'NBA', 'MLB', 'NHL'. Required for ESPN/Sleeper and Fantrax name lookups.
typesNoFilter to these types. Omit for all.
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).
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. Changed16 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 / types / description
      Previous value: -"Filter to these transaction types. Omit for all."New value: +"Filter to these types. Omit for all."
    • changedInput schema / properties / week / description
      Previous value: -"Week/scoring period. Sleeper requires a week (defaults to current). ESPN/Fantrax return recent moves regardless."New value: +"Week/scoring period (Sleeper defaults to current)."
    • removedInput schema / required
      Removed value: -[
-  "provider"
-]
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

The description goes well beyond the read-only Hint by disclosing important behavioral nuances: profile-first league inference, newest-first ordering, per-platform differences (FAAB bids for Sleeper, partial trade legs on ESPN, public-only visibility on Fantrax). This prepares the agent for platform-specific results beyond a generic 'get transactions'.

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 compact, front-loaded, and information-dense. Every sentence serves a purpose: the first defines scope, the second gives usage context, and the third covers platform-specific caveats. No filler or repetition of the title.

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?

The description covers what the tool returns, ordering, league inference, and key per-platform differences. It does not describe output schema or fields, but given this is a list retrieval operation, the level of context is adequate for an agent to decide when to call it and what to expect. A minor gap is lack of explicit error/auth context (e.g., Fantrax public-only).

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?

With full schema parameter descriptions, the description still adds value by explaining profile-first league inference (why league_id may be omitted) and by reinforcing 'newest first' ordering semantics for limit. It also introduces functional context (FAAB, trade legs) not present in the schema. It does not deeply explain sport or week across platforms, but those are covered in schema/type descriptions.

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 identifies the resource ('recent league moves') and enumerates the types of transactions (adds, drops, waiver claims, trades). It even provides user-facing example questions ('did my waiver claim process?') that make the purpose immediately understandable. The ordering ('newest first') further clarifies behavior.

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 usage context: 'Profile-first: league inferred when connected' tells the agent when league_id may be omitted quoted. It also provides per-platform call-outs (Sleeper per-week with FAAB, ESPN activity feed/trade-leg caveat, Fantrax public-only) that guide expectations. It does not explicitly name alternative sibling tools, but the platform notes supply usable decision context.

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