Skip to main content
Glama

sleeper_status

Verify your Cotlet.dev account, available credits, and Sleeper connection are ready before using fantasy football tools.

Instructions

Check that your Cotlet.dev account and Sleeper are ready: account, credits and Sleeper connection.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden, and it does little beyond naming the three things checked. It never says whether the tool returns statuses or raises an error on failure, whether it consumes credits, or whether it has any side effects — for a diagnostics tool those are the details an agent needs.

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 verb first and the checked items listed compactly; nothing is wasted. The colon-list construction is slightly awkward but not padded.

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?

With no annotations and no output schema, the description is the only source of truth about what this returns, and it stops at naming the checks without describing the shape of the result (per-check status, booleans, error conditions). For a zero-parameter diagnostic tool it is adequate but leaves a real gap around return semantics.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is no parameter meaning to convey and the baseline of 4 applies. The description correctly implies no inputs are required.

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?

The description gives a specific verb ('Check') and a specific object ('account and Sleeper ... ready'), then enumerates the three things verified: account, credits, Sleeper connection. That distinguishes it from the action-oriented siblings (open, close, click, read, type) as a pre-flight health check, though it never explicitly contrasts itself with them.

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: 'check that ... are ready' suggests calling before doing other Sleeper work, but there is no explicit when-to-use, no when-not-to-use, and no named alternative among the siblings. An agent can infer the pre-flight role but must guess at the trigger conditions.

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