Skip to main content
Glama
Sign In

GlossGenius MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

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 GlossGenius it serves these actions: List appointments, Book appointment, Reschedule appointment, Find client, Get sales summary.

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

A4.3/5.0
Behavior5/5

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

Beyond the annotations (readOnly, openWorld, non-idempotent, non-destructive), the description discloses the credentialed environment ('a real Chrome on Cotlet, where the user is signed in to their sites'), the tab-routing behavior (existing site tab first, else a new tab, preserving the user's tabs), and what comes back after the call. That is exactly the behavioral context an agent needs to avoid re-authenticating or disturbing session state.

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 core action and sequencing cue, then tab behavior, then return value. Dense but mostly earned; the trailing list of GlossGenius actions is useful for routing though arguably belongs to the app guide tool rather than here.

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?

There is no output schema, so the description usefully covers what the call returns (in-view elements and text with stable numbering). For a session-launching tool with only two optional parameters this is nearly complete; it does not mention session lifecycle or when to use the close sibling, a minor omission.

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% and the schema already explains both `app` (including the slug pattern and the 'leave it out' default) and `url` in greater detail than the description. The description adds no formatting or defaulting semantics beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource: starts the user's Cloud Browser (a real Chrome on Cotlet) and opens the given url. It is clearly distinguishable from the other browser_* siblings because it is the entry point that launches the session, and the phrase 'Call it first' plus the return description ('answers the page after it') pins down its role.

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, and the sentence about the `app` parameter explains when the step runs in the user's own browser vs. an app's Cloud Browser. It also enumerates the GlossGenius actions served, which helps an agent decide this is the right starting point. It stops short of explicitly contrasting with cotlet_browser_navigate, which would have made it a 5.

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

All GlossGenius MCP Server and API by Cotlet toolsInspect
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