Skip to main content
Glama

sleeper_open

Opens a Sleeper page in your signed-in Cloud Browser so you can manage leagues, lineups, waivers, and trades. Specify a URL or use the default https://sleeper.app.

Instructions

Open a Sleeper page in your signed-in Cloud Browser (default https://sleeper.app) to work with leagues, lineups, waivers and trades.

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_open"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoPage to open. Default: https://sleeper.app

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It does disclose one genuinely useful trait — the browser is already signed in, so no auth step is needed — but it omits navigation semantics such as whether opening replaces the current page, opens a new tab, or fails on a bad URL.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with the default value parenthesized right where it matters. The closing 'to work with leagues, lineups, waivers and trades' adds domain flavor rather than operational detail, a minor bit of padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-optional-parameter navigation tool with no output schema, the definition supplies the URL default, the execution environment, and the auth state. Nothing essential to invoking it correctly is missing.

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?

Only one optional parameter exists and schema coverage is 100%, so the schema already documents the url field. The description restates the default rather than adding meaning such as accepted URL forms or relative paths, which is the baseline 3 case.

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?

Names a specific verb and resource: opening a Sleeper page in the signed-in Cloud Browser, with the default URL spelled out. It partially distinguishes it from siblings like sleeper_click and sleeper_read by framing it as navigation, but the trailing clause 'to work with leagues, lineups, waivers and trades' describes the domain rather than what this tool uniquely does.

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 opens the page that later click/read/type calls act on, but the description never says so, never states it is the prerequisite first step, and never gives a when-not to use it (e.g., if a page is already open).

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