Sleeper MCP Server

Trending Players

get_trending_players

Read-only

Identify the most added or dropped players in a sport to track waiver wire trends.

Instructions

Get trending players (most added or dropped).

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_trending_players"
  }
}

Input Schema

Name	Required	Description	Default
`sport`	No		nfl
`add_drop`	No		add

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 29, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the agent knows it's a safe read operation. The description adds only the concept of 'trending' but does not elaborate on data freshness, pagination, or limits. This is adequate but not exceptional.

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 a single sentence and is concise. However, it could be slightly more structured (e.g., separating the parameter explanation). The brevity is valuable, but the lack of parameter details reduces efficiency for agents.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has an output schema (external to the description), so the omission of return format is acceptable. However, the description does not provide usage context (e.g., 'Use this to see popular player movements') or edge cases. It is minimally complete for a simple tool.

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 0%, so the description must compensate. The phrase 'most added or dropped' hints at the add_drop parameter but does not explicitly explain that 'add' returns most added players and 'drop' returns most dropped. The sport parameter is entirely undescribed. This provides minimal additional meaning beyond the enum and default values.

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 trending players, with the parenthetical 'most added or dropped' directly linking to the add_drop parameter. This distinguishes it from tools like search_players (for specific player searches) and get_player_stats (for stats).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no explicit guidance on when to use this tool versus alternatives like search_players or get_player_stats. The sibling list is external, and the description itself lacks context for selection.

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

Deploy Server