Skip to main content
Glama
Sign In
Sports Hub MCP Server

Sports Hub MCP Server

by lacausecrypto
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

sleeper: Search players

sleeper_search_players
Read-onlyIdempotent

Search Sleeper NFL players by name, team, or position and return compact records with injury status, depth-chart order, team, and position.

Instructions

Search the Sleeper NFL player database by name (and optionally team/position). Returns slim records with injury status, depth-chart order, team and position. The full player set is cached for 24h.

Input Schema

NameRequiredDescriptionDefault
teamNoFilter by team abbreviation (e.g. KC, BUF)
limitNoMax results (default 25)
queryYesName (full or partial), case-insensitive
fieldsNoKeys to keep (comma-separated).
positionNoFilter by position (e.g. QB, RB, WR, TE)

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

A4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/openWorld, so the safety bar is met elsewhere. The description still adds real behavioral value: it discloses the return shape ('slim records with injury status, depth-chart order, team and position') and the 24h cache TTL, which tells the agent results may be stale. No mutation, auth, or rate-limit details are given, but none are needed for a read-only search.

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 tight sentences with no filler; the search purpose and optional filters are front-loaded before the return/cache details.

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?

With no output schema, the description correctly carries the return-value burden by naming the fields returned, and it flags cache freshness. It is close to complete; only pagination/limit behavior is left to the schema.

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 the baseline is 3. The description restates the name/team/position filters that the schema already documents and does not mention the 'fields' or 'limit' parameters, so it adds little beyond the structured field definitions.

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 gives a specific verb ('Search'), the exact resource ('Sleeper NFL player database'), and the search key ('by name (and optionally team/position)'). The 'Sleeper NFL' qualifier cleanly separates it from the sibling player searches (sportsdb_search_players, mlb_search_players, opendota_search_players) and from sleeper_get_user/sleeper_get_trending_players.

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 by 'search ... by name', but there is no explicit guidance on when to reach for this over siblings such as sleeper_get_trending_players or the league/roster tools, and no stated exclusions or prerequisites. Adequate but not directive.

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