Rosy Salon Software 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 Rosy Salon Software it serves these actions: View appointment schedule, View client details from an appointment, View arrival check-in status.

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.2/5.0

Behavior5/5

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

Annotations already carry the safety profile (readOnlyHint, openWorldHint, destructiveHint=false), and the description still adds real behavior: it discloses that the browser is a real signed-in Chrome session, that the URL lands in the site's existing tab or a new tab so the user's tabs are untouched, and that the response is a page snapshot of visible elements and text with matching element numbers. That return-shape disclosure matters a lot given there is no output schema.

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 ordering instruction, then behavior, then return shape. Slightly overstuffed by the trailing Rosy Salon action enumeration, which reads like appended routing metadata rather than core definition, but every earlier sentence earns its place.

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?

No output schema exists, and the description compensates by describing what comes back after the page loads. For a tool whose complexity comes from real-browser session state, the main omission is failure behavior — unsigned-in state, redirects, or popups — which an agent would want before relying on the call.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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, but the description earns more by explaining the routing semantics of `url` (same-site tab reuse versus new tab). The `app` parameter is left entirely to the schema, whose parenthetical about `cotlet_app_guide` already handles it adequately.

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?

Names a specific verb and resource: starts the user's Cloud Browser (a real Chrome where the user is signed in) and opens `url`. The tab-placement detail makes the effect concrete. It stops short of differentiating itself from the sibling `cotlet_browser_navigate`, so an agent must guess between open and navigate.

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 for a browser workflow, and the Rosy Salon action list tells the agent which tasks this entry point serves. It gives no when-not guidance and never contrasts with `cotlet_browser_navigate`, `cotlet_browser_tabs`, or `cotlet_browser_read`, which are the closest alternatives.

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

All Rosy Salon Software 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?