Skip to main content
Glama
Sign In

Booksy MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

Open the browser

cotlet_browser_open
Read-only

Starts the user's Cloud Browser (a real Chrome on Cotlet, where the user is signed in to their sites) and opens url. Call it first. The URL goes to the site's open tab, else to a new tab, so the user's own tabs stay. Answers the page after it: the elements and text in view, with the same numbers. In Booksy it serves these actions: List bookings, Create booking, Reschedule booking, Reply to review, Read reports.

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

Input Schema

NameRequiredDescriptionDefault
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.
urlNoA public http or https address, e.g. https://example.com.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / app
      Added value: +{
+  "description": "Leave 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.",
+  "pattern": "^[a-z0-9][a-z0-9-]{0,79}$",
+  "type": "string"
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / url / description
      Previous value: -"A public http or https address, e.g. https://example.com. In an app's browser, a page of that app."New value: +"A public http or https address, e.g. https://example.com."
  3. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint, openWorldHint, idempotentHint=false), the description discloses meaningful behavior: the browser is the user's real signed-in Chrome, existing user tabs are preserved, and the call answers with the visible page state using the same element numbering. It does not mention auth/session prerequisites or failure modes for private URLs (though the `app` pattern hints at restrictions).

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?

Front-loaded with the core action and the 'call it first' directive, then supporting detail. The trailing Booksy action list is long but does serve to connect this tool to the booksy_* siblings; it is borderline padding.

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 compensates by describing the return value (visible elements and text with stable numbering). For a two-parameter entry-point tool this is nearly complete; only the `app` override and any error behavior are left unaddressed.

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 baseline is 3. The description adds useful routing semantics for `url` (existing tab vs. new tab), but says nothing about the `app` parameter's role, leaving that entirely to the schema.

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 and resource: 'Starts the user's Cloud Browser ... and opens `url`', and adds the qualifier that it is a real Chrome where the user is signed in. It does not, however, distinguish itself from the sibling `cotlet_browser_navigate`, which an agent could plausibly confuse with 'open a URL'.

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?

Explicit sequencing guidance is given: 'Call it first', which tells the agent this is the entry point before click/type/read steps. It also explains tab-routing behavior ('goes to the site's open tab, else to a new tab'), but offers no when-not guidance or contrast with `cotlet_browser_navigate`.

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

All Booksy MCP Server and API by Cotlet toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources