Skip to main content
Glama

Pabau 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 Pabau it serves these actions: View appointments and navigate calendar dates and Day/Week/Month views, Filter the calendar by locations, employees/teams, statuses and services, Hide client details on the calendar display.

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. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Goes well beyond the annotations (readOnlyHint, openWorldHint, idempotentHint=false) by disclosing where the URL lands (site's existing tab, else a new tab, leaving the user's tabs intact) and what answers the call (the elements and text in view, with matching numbers). That is exactly the side-effect and return-shape context annotations cannot express. It omits failure modes such as what happens with a non-public URL or a signed-out session.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first three sentences are front-loaded and earn their place: purpose, ordering, tab behavior, return content. The closing sentence, however, is a dangling list of site-specific Pabau capabilities ('View appointments and navigate calendar dates and Day/Week/Month views...') that reads as injected content and does not describe this tool's behavior, adding bulk without guidance.

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 only two fully documented parameters and no output schema, the description supplies the missing return information ('the elements and text in view, with the same numbers') and the tab-reuse side effect, which is what an agent needs to call it correctly and parse the answer. The Pabau action list is extraneous rather than compensatory, but nothing essential is missing.

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 leave-it-out default for `app`. The description reinforces `url` behavior (open tab vs new tab) but adds no syntax or format detail beyond the schema. Baseline 3 is appropriate when the schema carries the parameter burden.

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?

States a specific verb and resource: starts the user's Cloud Browser (a real Chrome on Cotlet where the user is signed in) and opens `url`. This distinguishes it from cotlet_browser_navigate and the other browser siblings by establishing it as the entry point. The trailing sentence about Pabau actions muddies rather than clarifies the core purpose.

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 sequencing guidance that an agent can act on immediately, and the `app` parameter guidance in the schema clarifies the default (user's web browser) versus an app-specific Cloud Browser. It stops short of naming when to use cotlet_browser_navigate instead for subsequent navigation, so the boundary with the closest sibling is left implicit.

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