Skip to main content
Glama
lacausecrypto

Sports Hub MCP Server

by lacausecrypto
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

sleeper: Get nfl state

sleeper_get_nfl_state
Read-onlyIdempotent

Retrieve the current NFL season, week, and season type (pre/regular/post/off) tracked by Sleeper to sync schedules and analysis.

Instructions

Get the current NFL season, week, and season type (pre/regular/post/off) as tracked by Sleeper.

Input Schema

NameRequiredDescriptionDefault
fieldsNoKeys to keep (comma-separated).

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.8/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/openWorld, so safety is covered. The description adds value by disclosing the returned content (season, week, season type tracked by Sleeper), which matters since there is no output schema. It does not mention refresh cadence or staleness, hence not a 5.

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?

A single front-loaded sentence with no filler; the core resource leads and the clarifying enum parenthetical trails appropriately.

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 trivial read-only state getter with one optional param and no output schema, the description covers the essentials by naming what is returned. It is nearly complete, though noting it is the canonical source for season/week context in sibling queries would make it fully self-sufficient.

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 100% for the single optional 'fields' parameter, so the schema already documents it fully. The description adds nothing about projecting fields or the comma-separated syntax, 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?

It states a specific verb ('Get') and resource ('NFL season, week, and season type') and even enumerates the return values with an enum-like gloss (pre/regular/post/off). The purpose is unambiguous because no sibling tool retrieves NFL state, but the description does not explicitly contrast itself with siblings.

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 only implied: an agent can infer this is the reference for the current season/week used to scope other queries, but the description never says when to call it or what it is a prerequisite for. No alternatives or exclusions are named.

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