Skip to main content
Glama

sleeper_click

Clicks a numbered element on the current Sleeper page to navigate or act on it. Use the element number from the last read to trigger that specific action.

Instructions

Click a numbered element on the current Sleeper page.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "element": "<element>"
    },
    "name": "sleeper_click"
  }
}

Input Schema

NameRequiredDescriptionDefault
elementYesElement number from the last read.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and does not meet it. It does not say what a click does to the page state, whether it can navigate away or trigger destructive actions, whether element numbers become stale after the click, or what the tool returns.

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?

One short sentence, front-loaded with the action and target, with no filler. It is efficient, though its brevity contributes to the missing behavioral detail rather than being purely a virtue.

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

Completeness1/5

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

This is a side-effecting UI action tool with no annotations and no output schema, so the description is the only source of behavioral context and it provides none beyond the action name. An agent cannot tell whether clicking navigates, mutates, or invalidates prior element numbering.

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?

The single parameter has 100% schema description coverage ("Element number from the last read"), so the schema already explains its meaning and the description adds no format or edge-case detail. This is the baseline case where the schema does the work.

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?

"Click a numbered element on the current Sleeper page" gives a specific verb (click) and a specific target (numbered element on the current page), which distinguishes it from siblings like sleeper_read or sleeper_type. It does not explicitly name a sibling, so it stops short of a 5.

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?

The phrase "from the last read" in the schema and "numbered element" in the description imply the read-then-click workflow, but the description never states prerequisites (must call sleeper_read first) or when to prefer sleeper_type over a click. Usage is inferred rather than stated.

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