Skip to main content
Glama

sleeper_read

Reads the current Sleeper page and returns its text plus numbered buttons, links, and fields, optionally scoped to one element. Use it to inspect page content before acting.

Instructions

Read the current Sleeper page: its text and numbered buttons, links and fields.

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

Input Schema

NameRequiredDescriptionDefault
elementNoRead only inside this element.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4/5.0
Behavior3/5

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

The description provides useful operational behavior by listing the types of elements it scrapes, going beyond basic function. However, since no annotations exist, it lacks disclosure on things like failure modes or return data structure specificity.

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?

The definition is highly efficient, using a single sentence to maximize clarity and avoid any superfluous language. It is well-front-loaded with necessary functional information.

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?

Given its low complexity (a single read operation), the description provides all necessary high-level context for an AI agent to determine its suitability. It successfully defines the scope of information it delivers.

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?

Since schema coverage is 100%, the tool parameters are fully defined in the input schema. The description focuses on the output content rather than explaining the specific function or constraints of the `element` input parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly defines the tool's function as reading the Sleeper page and specifies the types of data it captures (text, buttons, links, fields). This distinguishes it as an observational tool, distinct from action-oriented siblings like `sleeper_click`.

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?

While it does not explicitly state 'use this when data retrieval is needed,' the description strongly implies its use case relative to the action-based sibling tools. Its purpose is unambiguously data gathering rather than manipulation.

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