ClubReady 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 ClubReady it serves these actions: Search customer or prospect profiles, View a customer profile, View customer amenities.

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 12, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Annotations only declare read-only, open-world, non-idempotent, non-destructive; the description adds real substance beyond that — the browser is authenticated as the user, the URL lands in the site's existing tab or a new tab so the user's own tabs are preserved, and the call returns the in-view elements and text with matching numbers. That is exactly the auth and side-effect context an agent needs before calling.

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 critical instruction ('Call it first') is front-loaded and there is no filler. Some sentences are telegraphic to the point of being slightly hard to parse — 'Answers the page after it: the elements and text in view, with the same numbers' — which costs a bit of readability.

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 does the work of explaining the return value, and it covers auth context, tab side effects, and call ordering for a tool that is the entry point of a browser session. It leaves one gap: idempotentHint=false implies repeat calls matter, but the description never says what happens if the browser is already started.

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%, including a detailed `app` description and a URL format example, so the schema carries the parameter burden. The description reinforces URL behavior (existing tab vs new tab) but never mentions the `app` parameter or when its default of the user's own browser should be overridden.

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?

The description states a specific verb and resource — 'Starts the user's Cloud Browser ... and opens `url`' — and clarifies what that browser actually is (a real Chrome where the user is signed in). 'Call it first' plus the tab-routing rule distinguishes it from cotlet_browser_navigate and the other browser siblings without the agent needing to open 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?

It gives explicit ordering guidance ('Call it first') and explains tab-selection behavior, so the agent knows this is the entry point rather than a follow-up navigation. It also scopes usage to concrete ClubReady actions, though it does not state any when-not conditions or name an alternative for re-opening an already-running browser.

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

All ClubReady 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?