TotalCoaching 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 TotalCoaching it serves these actions: List clients and activation status, Read client profile, Read client training calendar.

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

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnly/openWorld/non-idempotent/non-destructive, so the description's real contribution is the session model (the user's authenticated Chrome) and the tab-placement rule (existing site tab, else new tab, user tabs preserved). It also discloses what comes back ('the elements and text in view, with the same numbers'), which the annotations do not cover. Failure modes and session lifetime are not described.

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 action and the identity of the browser, and the ordering instruction follows immediately. The trailing TotalCoaching action list ('List clients and activation status, Read client profile, Read client training calendar') is a bit of an inventory dump that adds volume more than invocation 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 optional parameters and no output schema, the definition is close to complete: it explains the execution environment, tab behavior, and the shape of the response. The phrase 'with the same numbers' is underspecified — an agent needs to know those numbers are the references used by click/find/read to be fully confident.

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%, and the schema itself explains the `app` escape hatch in detail, so the baseline is 3. The description adds meaning for `url` by explaining where the target lands (site's open tab vs new tab), but contributes nothing about `app` or the URI format beyond what the schema already says.

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 ... and opens `url`') and qualifies what the browser actually is (a real Chrome where the user is signed in). It positions itself as the entry point with 'Call it first', but never distinguishes itself from the sibling cotlet_browser_navigate, which plausibly also loads URLs.

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 an explicit ordering rule relative to all the other browser tools, and the TotalCoaching sentence signals the intended downstream use case. There is no when-not guidance, though, and the overlap with cotlet_browser_navigate is left for the agent to guess.

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

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