CharlieHR 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 CharlieHR it serves these actions: List team members, List time off requests, Approve time off request, Deny time off request, Book time off, Record sick day, Adjust time off allowance, Cancel time off booking, Offboard team member.

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

A3.9/5.0

Behavior4/5

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

Beyond the annotations, it discloses meaningful behavior: the URL targets the site's existing tab before opening a new one, user tabs are preserved, and the call returns the visible elements and text of the resulting page. That is real added context for a read-only, open-world tool. It does not cover session lifetime or what happens if the browser is already running.

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?

The core behavior and the 'call it first' instruction are front-loaded in the opening sentences with little waste. The trailing enumeration of nine CharlieHR actions is bulky and reads as retrieval padding rather than operational 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?

With no output schema, the description usefully explains that the response is the resulting page's elements and text. The phrase 'with the same numbers' is left unexplained, so an agent may not know it refers to element indices reusable by the click/type siblings.

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%, so both `app` and `url` are already fully documented in the input schema, including the slug pattern and http/https requirement. The description's only added meaning is the tab-routing behavior of `url`, which is modest; the baseline 3 applies.

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?

The description names a specific verb and resource ('Starts the user's Cloud Browser ... and opens `url`') and clarifies it is a real Chrome session where the user is signed in. It distinguishes itself by ordering ('Call it first'), though it never explicitly contrasts with the sibling cotlet_browser_navigate, leaving that boundary to inference.

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 the browser toolset, and the app-parameter note ties usage to cotlet_app_guide naming an app's own Cloud Browser. It lacks an explicit when-not-to-use statement (e.g., versus navigate for subsequent page loads), so it stops short of full routing guidance.

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

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