Skip to main content
Glama
Sign In
Sports Hub MCP Server

Sports Hub MCP Server

by lacausecrypto
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

sleeper: Get trending players

sleeper_get_trending_players
Read-onlyIdempotent

Fetch the most-added or most-dropped NFL players over a chosen lookback window, with names, teams, and positions. Use it to gauge fantasy football buzz and roster movement.

Instructions

Get the most-added or most-dropped NFL players over a lookback window, enriched with names/teams/positions. Doubles as a crude buzz signal.

Input Schema

NameRequiredDescriptionDefault
typeYes'add' (most added) or 'drop' (most dropped)
limitNoMax results (default 25)
fieldsNoKeys to keep (comma-separated).
lookback_hoursNoLookback window in hours (default 24)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.4.1
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • addedInput schema / properties / fields
      Added value: +{
+  "description": "Keys to keep (comma-separated).",
+  "type": "string"
+}
  2. Addedv1.3.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds that results are 'enriched with names/teams/positions', which is useful context about what comes back, but says nothing about ordering, rate limits, or pagination behavior.

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?

Two tightly written sentences with the operation front-loaded and no filler. The second sentence adds a genuinely different angle (trend/buzz signal) rather than padding.

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?

There is no output schema, so the description carries some burden to describe the return, and 'enriched with names/teams/positions' partially discharges that. With annotations covering safety and 100% schema coverage on all four params, only the exact return shape/ordering is left unstated.

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 description coverage is 100%, so type, limit, fields, and lookback_hours are all documented in the schema itself. The description's 'most-added or most-dropped' and 'lookback window' merely restate what the schema already conveys, adding no syntax or format detail beyond it.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource ('Get the most-added or most-dropped NFL players') plus the scoping qualifier ('over a lookback window'), which is inherently distinct from sibling tools like sleeper_search_players. It is clear what the tool does, though it never explicitly names an alternative sibling to route against.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: the lookback window and the phrase 'Doubles as a crude buzz signal' hint at when this is useful (trend detection rather than lookup), but there is no explicit when-to-use, when-not-to-use, or named alternative such as sleeper_search_players.

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