Mariana Tek MCP Server and API 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 Mariana Tek it serves these actions: List classes, Book reservation, Cancel reservation, Find customer, Add class credits.

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

TDQS

A4.4/5.0

Behavior5/5

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

Annotations only cover the safety profile (readOnly, openWorld, non-destructive, non-idempotent); the description adds the important behavioural facts: the session runs in the user's authenticated Chrome, the URL is routed to the site's existing tab before a new one so the user's tabs are preserved, and it returns the visible elements and text with numbering for follow-up calls. Those are exactly the details an agent needs and none are recoverable from the annotations.

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?

Short and front-loaded: what it does, when to call it, then the tab and return behaviour. It is densely packed into a few sentences with no filler, though the final app-action list reads as a bolt-on rather than integrated guidance.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 compensates by describing the response (elements and text in view with consistent numbers) so the agent knows what comes back. Auth context, tab side effects, and the action coverage are all present for a two-parameter entry-point tool.

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%, so both `app` and `url` are already documented, including the unusual 'leave it out' default for `app`. The description's only added meaning is the tab-routing behaviour of `url`, which is marginal 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?

The description names a specific verb and resource — starts the user's Cloud Browser and opens `url` — and qualifies what that browser is (a real Chrome where the user is already signed in). The 'Call it first' instruction and the Mariana Tek action list make its role as the entry point unambiguous.

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 a clear ordering rule ('Call it first') and concrete context for the Mariana Tek flows (List classes, Book reservation, Cancel reservation, Find customer, Add class credits). It never states when to use a sibling like cotlet_browser_navigate instead, so the exclusion side of the guidance is missing.

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

All Mariana Tek MCP Server and API 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?