Skip to main content
Glama
yooitsgreg

sleeper-mcp

by yooitsgreg

Get All NFL Players

sleeper_get_nfl_players
Read-onlyIdempotent

Retrieve NFL player data from Sleeper with filters for position, team, active status, and name search. Supports pagination.

Instructions

Fetch the complete NFL player database from Sleeper (~5MB). Returns all player metadata. NOTE: This is a large dataset. Use filters to narrow results. Sleeper recommends caching this data and only fetching once per day.

Args:

  • position_filter (string, optional): Filter by position (e.g. "QB", "RB", "WR", "TE", "K", "DEF")

  • team_filter (string, optional): Filter by NFL team abbreviation (e.g. "KC", "SF", "DAL")

  • active_only (boolean): Only return active players (default: true)

  • search (string, optional): Filter by player name (case-insensitive substring match)

  • limit (number): Max players to return (default: 50, max: 200)

  • offset (number): Pagination offset (default: 0)

Returns: Paginated list of players with id, name, position, team, status.

Examples:

  • "List all active QBs"

  • "Find players on the Kansas City Chiefs"

  • "Search for players named 'Patrick'"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax players to return
offsetNoPagination offset
searchNoCase-insensitive substring match on player name
active_onlyNoOnly return active players
team_filterNoFilter by NFL team abbreviation (e.g. KC, SF, DAL)
position_filterNoFilter by position: QB, RB, WR, TE, K, DEF, etc.
Behavior4/5

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

Annotations already indicate read-only, idempotent, and non-destructive behavior. The description adds value by disclosing the ~5MB size, caching recommendation, and return fields (id, name, position, team, status). 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with a clear main sentence, a note, then structured Args, Returns, and Examples sections. It is front-loaded and each section earns its place, though slightly lengthy.

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?

Given no output schema, the description fully explains return fields and pagination. It covers size, caching, and filter usage. All important aspects for a data-fetching tool with 6 parameters are addressed.

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?

Input schema has 100% coverage with descriptions for all 6 parameters. The description repeats them in an Args list and adds usage examples, providing minor additional clarity but no new semantic meaning beyond 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 fetches the complete NFL player database from Sleeper and returns all player metadata. It distinguishes itself from sibling tools as the only player-fetching tool. The size and caching note add specificity.

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 explicitly notes the large dataset size and recommends using filters and caching once per day. It implies usage context but does not directly compare with alternatives, though no alternative player tools exist.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/yooitsgreg/sleeper-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server