Resource Guru 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 Resource Guru it serves these actions: List bookings, Create booking, Confirm tentative booking, Approve or decline booking, Add time off, Create project.

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.3/5.0

Behavior4/5

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

Beyond the annotations (readOnlyHint, openWorldHint, non-idempotent), it discloses that the URL reuses the site's existing tab before opening a new one and that the user's own tabs are preserved, plus what comes back ('elements and text in view, with the same numbers'). It does not cover failure modes such as an unreachable URL, session expiry, or sign-in state loss, which matter for an open-world tool.

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 guiding instruction ('Call it first') is front-loaded and the tab-reuse rule follows immediately. The trailing Resource Guru action list is useful disambiguation but reads as appended context rather than core definition.

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 only two optional parameters and no output schema, the description carries the return-shape burden and does so via 'Answers the page after it: the elements and text in view.' Remaining gaps are edge-case behavior (failed loads, profile/session state) rather than anything blocking a correct first call.

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 the baseline is 3, but the description adds real meaning: the app parameter is defaulted to the user's own browser and only used for app-specific Cloud Browsers, and the url parameter is explained in terms of tab-targeting behavior rather than just being a URI.

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 action (starts the Cloud Browser and opens a URL) and pins the ordering with 'Call it first,' which distinguishes it from the navigation/read siblings that operate on an already-open page. The 'real Chrome on Cotlet, where the user is signed in' clause identifies the resource concretely.

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 explicit sequencing ('Call it first') and tells the agent when to supply the app slug ('Only when cotlet_app_guide names an app's own Cloud Browser') versus leaving it out. It stops short of naming cotlet_browser_navigate as the alternative for an already-open browser, 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 Resource Guru 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?