Skip to main content
Glama
Sign In
Sports Hub MCP Server

Sports Hub MCP Server

by lacausecrypto
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

sleeper: Get league matchups

sleeper_get_league_matchups
Read-onlyIdempotent

Fetch weekly fantasy football matchups for a league, returning roster IDs, points, and starters by NFL week.

Instructions

Get the matchups for a league in a given week (roster_id, points, starters).

Input Schema

NameRequiredDescriptionDefault
weekYesNFL week number
fieldsNoKeys to keep (comma-separated).
league_idYesLeague id

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

B3.4/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 contributes the returned fields, but discloses nothing about auth requirements, empty weeks, or scoring semantics. Adequate but not rich.

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?

One sentence, front-loaded with the verb and resource, with the returned-field list parenthetical. No filler.

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?

For a simple read tool with no output schema, the description usefully previews the return payload (roster_id, points, starters), which compensates for the absent output schema. Minor gaps remain around what a 'matchup' pairing means.

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% with only three parameters, so the schema already documents league_id, week, and fields. The description adds no format or constraint detail beyond that, so baseline 3 applies.

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?

States a specific verb (get) and resource (league matchups) scoped to a week, and names the payload fields returned (roster_id, points, starters). This clearly separates it from siblings like sleeper_get_league_rosters and sleeper_get_league_users, though it doesn't name them explicitly.

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?

No when-to-use guidance, no alternatives, no exclusions. The required parameters imply a scenario (weekly head-to-head scoring for a fantasy league), but the description never states the context or routing conditions.

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