Bokadirekt MCP Server and API by Cotlet

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 Bokadirekt it serves these actions: List bookings, Create booking, Move booking, Cancel booking, Find available times, List customers, Send booking message, List waitlist.

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

Name	Required	Description	Default
`app`	No	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.
`url`	No	A public http or https address, e.g. https://example.com.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Beyond the annotations, the description discloses what actually happens: a real Chrome where the user is signed in, the URL reusing the site's existing tab or a new tab so the user's own tabs are preserved, and a return of visible elements and text with stable numbering. These are exactly the behavioral details an agent needs and that readOnlyHint/openWorldHint alone cannot convey. Nothing contradicts the annotations.

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?

The core behavior and the "call it first" instruction are front-loaded and dense with useful detail, and the sentences earn their place. The trailing list of Bokadirekt actions is somewhat tangential for a generic browser-open tool, though it does hint at downstream capability.

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

Completeness5/5

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

There is no output schema, yet the description explains what comes back (elements and text in view with consistent numbering), and the annotations cover the safety profile. Combined with a fully documented two-parameter schema, an agent has everything needed to call this correctly.

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 description coverage is 100%, so both `app` and `url` are already documented in the schema, including the fallback rule for `app`. The description adds a little context by explaining tab reuse for the URL, but does not elaborate on parameter meaning beyond the schema. 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 description states a specific verb and resource: it starts the user's Cloud Browser (a real signed-in Chrome on Cotlet) and opens `url`. It also describes tab-targeting behavior, so an agent can picture the effect. It does not distinguish itself from the sibling `cotlet_browser_navigate`, which plausibly does something similar, 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Call it first" gives explicit ordering guidance, telling the agent this is the entry point before other browser steps. The `app` parameter's schema note also explains when to leave it out and when to supply a slug. It gives no explicit when-not-to-use case or a direct comparison 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 Bokadirekt MCP Server and API by Cotlet tools Inspect

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

Need Help?