CoachingPortal 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 CoachingPortal it serves these actions: List clients, Get client progress, Invite client, Review application, Edit intake form, Publish intake form, Set client active, Add progress entry, Adjust client targets, Update client tracking, List check ins, Respond to check in, Append check in note, List check in schedule, List programs, Create program template, Edit program template, Assign program, List meal plans, Create meal plan, Assign meal plan, Manage recipe book, Assign recipe book, List habits, Configure client habit, List messages, Send message, List community, Create team chat, Publish challenge, Create leaderboard, Get coaching analytics, List resources, Add resource, Attach client resource, List coaches, Invite coach, Set calculation defaults, Configure check in questions, Publish announcement, Duplicate program, Share program, Manage custom exercise, Manage workout block, Edit meal plan, Manage coach invitation, Reassign coach clients, Generate check in draft, Create progress story, Set adherence weights, Set weight tracking policy, Get dashboard, Remove client invitation, Delete client, Update client profile metrics, Manage movement screen, Search exercises, Delete program template, List workout blocks, Duplicate meal plan, Share meal plan, Delete meal plan, Calculate meal plan targets, List recipe books, Delete recipe book, Search food library, Import food to plan, Favorite food, Generate progress summary, Generate training draft, Generate meal plan draft, Discard ai draft, Get ai credit balance, Get coach referrals, List pt sessions, Manage pt session, Log pt workout, Update workspace branding, Manage landing page, Update coach profile, Set workspace units, Get subscription, Manage subscription, Submit feature request, Delete workspace or account, Get personal insights, Log personal progress, Manage personal food log, Log recipe today, Get grocery list, Read meal recipe, Manage personal workout, Create workout share image, Submit personal check in, Log habit completion, Manage self coaching habits, Manage challenge membership, Refresh leaderboard, Upload progress photo, Update personal profile, Configure training summary email, Dismiss announcement, Manage self coaching plan, Cancel challenge, Send voice message, Open pt join code, Set notification preferences, Manage connected accounts.

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

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, destructiveHint=false and idempotentHint=false, but the description adds real context beyond them: the session is a real Chrome where the user is signed in, the URL reuses the site's open tab rather than spawning a new one, and the user's own tabs are preserved. It also discloses the return shape (elements and text in view, with the same numbers) that the annotations cannot convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first two sentences are well front-loaded and efficient, but the remaining ~80% of the text is a flat dump of roughly one hundred CoachingPortal action names that does not help an agent decide whether or how to open a browser. That enumeration is unearned bulk and buries the operative 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?

For a two-parameter, zero-required browser-open tool with no output schema, the description covers ordering, tab routing, session identity, and an informal description of the returned page content. Nothing an agent needs to invoke it correctly is missing, though the action catalog adds length without adding completeness.

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 both `app` and `url` are documented in the schema with format and pattern constraints. The description adds only marginal meaning beyond that, mainly the tab-routing behavior for `url`; the `app` semantics are already fully carried by the schema text.

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 `url`, with the explicit sequencing cue "Call it first". This distinguishes it from the other browser siblings such as cotlet_browser_navigate or cotlet_browser_tabs, which act on an already-open session.

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 clear ordering guidance, and the schema-adjacent note that `app` should be left out unless cotlet_app_guide names an app's own Cloud Browser is a genuine when-to-use rule. It does not explicitly name a sibling alternative (e.g. navigate) for the case where a browser is already open, so the exclusion is implied rather than stated.

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

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