Skip to main content
Glama

Bookipi by Cotlet

Click on the page

cotlet_browser_click
Destructive

Clicks element element, or point x, y of the screenshot; double double-clicks, button: right right-clicks. Answers the page after it: the elements and text in view, with the same numbers. Says when nothing changed. A link that would open a new tab opens in this one. Buttons that pay or buy, and sign-in and account pages, are refused.

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": "cotlet_browser_click"
  }
}

Input Schema

NameRequiredDescriptionDefault
xNoInstead of `element`: pixels from the left of the screenshot.
yNoWith `x`: pixels from the top 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.
buttonNoright opens the page's own context menu. Default: left.
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.
doubleNoDouble-click.
elementNoThe element's number from the last read or step answer.
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

A4.3/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the bar is lower, yet the description still adds behavior not present in structured fields: it answers with the post-click page state (elements and text, same numbering), reports when nothing changed, redirects new-tab links into the current tab, and refuses payment and authentication flows.

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?

Four sentences, front-loaded with the action and zero filler; the return-behavior and refusal clauses each carry real weight. The telegraphic phrasing ('Says when nothing changed') is slightly elliptical, costing a bit of clarity for the compression.

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?

With no output schema, the description carries the return-value burden and does so by describing the page answer and the no-change case. For a destructive, open-world click tool, remaining gaps are timing/error behavior (waits, timeouts, failure answers) and the fact that `tab`, `app`, and `dialog` semantics are left entirely to the schema.

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 the schema already documents all nine parameters including enum values for `button` and `dialog`. The description only restates `element`/`x`,`y` targeting and the `double` and `button: right` modes, adding no syntax or edge-case meaning beyond what the schema says; baseline 3 applies.

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?

States a specific verb and resource ('Clicks element `element`, or point `x`, `y` of the screenshot') and immediately enumerates the variants (double-click, right-click), which separates it from siblings like hover, type, drag, or press without needing their schemas.

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?

Gives a concrete when-not: pay/buy buttons and sign-in/account pages are refused, which tells the agent to stop and reconsider. It also resolves a likely ambiguity (a link that would open a new tab opens in this one). What it lacks is explicit routing to alternatives such as hover or fill_form when a plain click is the wrong action.

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