Skip to main content
Glama

sleeper_guide

Get step-by-step guidance for navigating Sleeper leagues, lineups, waivers, and trades, including screens and the sign-in link; call this first to orient tasks.

Instructions

How to work in Sleeper (leagues, lineups, waivers and trades): its screens and the sign-in link. Call this first.

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": "sleeper_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskNoWhat you want done in Sleeper, in your words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations and no output schema, the description carries the full disclosure burden. It discloses content scope (screens, sign-in link) which is genuinely useful, but never says whether the result is reference text an agent should read versus something that alters state, nor how the returned guidance relates to the task argument.

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: scope first, the imperative 'Call this first' last, which is exactly the right emphasis for an entry-point tool. No filler or restated name.

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?

For a low-complexity single-parameter helper the essentials are there, but two agent-relevant questions go unanswered: what the response looks like (guide text vs. a link to follow) and whether the task argument tailors the guidance or is ignored.

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% and the single 'task' parameter is already documented in-schema as 'what you want done in Sleeper, in your words'. The description adds no meaning about how task shapes the output, 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 the resource concretely: an orientation guide for working in Sleeper, scoped to leagues, lineups, waivers, trades, plus screens and a sign-in link. That distinguishes it from the sibling set (click/close/open/read/status/type), which are UI primitives rather than documentation. It stops short of saying what form the guidance takes (text? URL? step list).

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

Usage Guidelines4/5

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

'Call this first' is explicit, unambiguous ordering guidance that selects this tool ahead of every sibling. What's missing is any statement of when to return to it later (e.g., on an unfamiliar screen) or whether it needs re-calling per task.

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