Skip to main content
Glama

Bookipi by Cotlet

Drag on the page

cotlet_browser_drag
Destructive

Drags from one element or point to another: a card between columns, a piece on a board, a slider's handle. Answers the page after it: the elements and text in view, with the same numbers.

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": {
      "from": "<from>",
      "to": "<to>"
    },
    "name": "cotlet_browser_drag"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesAn element number, or x and y of the screenshot.
appNoLeave it out: the step runs in the user's web browser. Only when cotlet_app_guide names an app's own Cloud Browser, that app's slug, e.g. milanote.
tabNoThe Tab id of the last answer. The step acts only while that tab is the shown one; if the user or another client showed another tab, it does nothing and answers tab_changed. Leave it out to act on the shown tab.
fromYesAn element number, or x and y of the screenshot.
dialogNoHow to answer a native dialog (confirm, prompt, 'leave this page?') this step opens: accept presses OK, dismiss presses Cancel. Default: OK for an alert, Cancel for every other dialog.
dialog_textNoText for a prompt dialog this step opens; implies accept.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / tab
      Added value: +{
      +  "description": "The Tab id of the last answer. The step acts only while that tab is the shown one; if the user or another client showed another tab, it does nothing and answers tab_changed. Leave it out to act on the shown tab.",
      +  "maxLength": 64,
      +  "minLength": 1,
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, openWorldHint=true and non-idempotent, so the safety profile is covered structurally. The description adds one genuinely new behavioral fact — that the call answers with the page state after the drag, using the same element numbering. It omits the tab_changed no-op case and the fact that a drag can trigger native dialogs, both of which are only in the schema.

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?

Two sentences, no filler, with the action front-loaded and the return behavior second. The closing clause 'with the same numbers' is slightly opaque and only decodable after reading the schema.

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?

For a 6-parameter, fully documented schema with no output schema, the description covers what the tool does and roughly what it returns (visible elements and text). The remaining gap — failure modes such as tab_changed and the destructive/irreversible nature of a drop — is partly carried by annotations, keeping this adequate but not exhaustive.

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%, so element/x-y targeting, app, tab, dialog and dialog_text are all documented in the schema. The phrase 'with the same numbers' mildly reinforces that element numbers come from the prior answer, but no coordinate, tab-consistency or dialog guidance is added beyond what the schema already says. 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?

The verb and resource are explicit: 'Drags from one element or point to another,' followed by three concrete scenarios (card between columns, piece on a board, slider handle) that pin down the interaction class. An agent can distinguish it from the click/hover siblings by the 'from ... to' semantics, though no sibling is named explicitly.

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 examples imply when dragging is the right action (reordering, moving, sliding), which is useful. But there is no explicit when-not guidance or comparison to cotlet_browser_click/hover, so the agent must infer that a simple press-and-release belongs elsewhere.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources