TrueCoach 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 TrueCoach it serves these actions: List clients, Create workout, Assign program, Read workout results, Message client.

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

Behavior4/5

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

Beyond the annotations, it explains that the session is a real Chrome where the user is already signed in, that the URL lands in the site's existing tab and otherwise a new tab so the user's own tabs survive, and that the call answers with the visible elements and text using the same numbering. That is meaningful disclosure of observable behavior and output shape for a tool with no output schema; only minor gaps remain, such as what happens if no session can be started.

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?

It is front-loaded with the core action and ordering instruction, and most sentences carry information an agent needs. The closing sentence listing TrueCoach actions is the weakest part – useful for scope but closer to a catalog than tool guidance, and 'with the same numbers' is slightly cryptic without seeing the referenced numbering scheme.

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?

For a browser-opening tool with no output schema, the description covers what happens (session start, tab targeting), when to call it, what it returns (visible elements and text), and how to treat the optional `app` parameter. Nothing critical is missing for an agent to invoke it correctly.

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 both parameters are already documented, but the description still adds value: it explains that a supplied URL is routed to the site's open tab or a new tab, and reinforces that `app` should normally be omitted. That is real semantics beyond the schema rather than restatement.

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 states a specific verb and resource – starts the user's Cloud Browser (a real signed-in Chrome) and opens a URL – and contrasts its role with the rest of the browser family by saying 'Call it first'. The follow-on sentence about returning page elements and text makes the tool noticeably distinct from a plain navigation action.

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 clear when-to-use guidance ('Call it first') and tells the agent to leave `app` unset unless cotlet_app_guide names a dedicated app browser. It never names an alternative such as cotlet_browser_navigate or explains when that should be preferred instead, so the routing guidance is contextual rather than exhaustive.

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

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