Skip to main content
Glama
Sign In
sleeper-mcp

sleeper-mcp

by yooitsgreg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get League Transactions

sleeper_get_league_transactions
Read-onlyIdempotent

Get all transactions (trades, waiver claims, free agent moves) for a specific week in a Sleeper league, including adds, drops, traded picks, and status.

Instructions

Get all transactions (trades, waiver claims, free agent adds/drops) for a specific round/week in a league.

Args:

  • league_id (string): The Sleeper league ID

  • round (number): The transaction round (corresponds to NFL week number)

Returns: List of transactions with type (trade/waiver/free_agent), adds, drops, traded picks, and status.

Examples:

  • "What trades happened in week 8 in league 123456?"

  • "Show all waiver claims for round 3"

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "league_id": "<league_id>",
      "round": "<round>"
    },
    "name": "sleeper_get_league_transactions"
  }
}

Input Schema

NameRequiredDescriptionDefault
roundYesTransaction round (week number)
league_idYesSleeper league ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, etc. The description adds useful behavioral context beyond annotations, such as the return format (list with type, adds, drops, etc.) and mapping of round to NFL week. No contradictions.

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 concise and well-structured: a brief purpose statement, bulleted args, returns, and examples. Every sentence adds value with no filler.

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?

For a simple read tool with 2 parameters, full schema coverage, and informative annotations, the description provides a complete picture of what the tool does and returns, including examples. No gaps.

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% with basic descriptions. The main description adds minimal extra information (e.g., round corresponds to NFL week, examples). Baseline 3 is appropriate as the schema already documents the parameters adequately.

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 gets all transactions for a specific round/week in a league, listing types like trades, waiver claims, and free agent adds/drops. It is distinct from sibling tools like sleeper_get_league_traded_picks which focus on traded picks only.

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 provides explicit context on when to use (e.g., 'Get all transactions for a specific round/week') and includes examples like 'What trades happened in week 8?'. However, it does not explicitly state when not to use this tool or mention alternatives, so it is slightly lacking in exclusion guidance.

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

Deploy Server

Other Tools