Sleeper MCP Server

NFL State

get_nfl_state

Read-only

Fetch the current NFL season, week, and season type from Sleeper to determine league state for scheduling and analysis.

Instructions

Get the current NFL season, week, and season type from Sleeper.

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": "get_nfl_state"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`leg`	No	Current leg
`week`	No	Current week (0 in offseason)
`season`	Yes	Active season year
`season_type`	Yes	pre, regular, post, or off
`display_week`	No	Week to display in UI
`previous_season`	No	Prior season year

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 29, 2026

TDQS

A4.5/5.0

Behavior4/5

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

The description matches the annotations (readOnlyHint=true, openWorldHint=true) and accurately describes the behavior as a read operation. While it does not add extra behavioral details beyond the annotations, the tool's simplicity means no additional disclosure is necessary.

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 a single, concise sentence that front-loads the purpose and returns exactly what the agent needs to know. No unnecessary words or information.

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 tool with no parameters and an output schema, the description succinctly states what is returned (season, week, season type), which is sufficient for the agent to understand and use the tool correctly.

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 tool has zero parameters, so the description does not need to add parameter details. Schema description coverage is 100%, meeting the baseline for no 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?

The description 'Get the current NFL season, week, and season type from Sleeper' uses a specific verb ('Get') and clearly identifies the resource (NFL state) and the data fields returned (season, week, season type). It is distinct from sibling tools like get_user_leagues or get_league_info, which focus on different aspects.

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 clearly states what the tool does, but does not explicitly mention when to use it versus alternatives. However, given its simplicity and the obvious context (retrieving current NFL state), the usage is self-evident and no conflicting alternatives exist among the listed siblings.

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

Deploy Server