Skip to main content
Glama

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 CrewNest it serves these actions: List customers, Update customer, Create customer, Import customers, Manage service address, Measure property, List jobs, Schedule job, List calendar, Reschedule job, Assign job, Configure recurring job, Update job status, Cancel job, Optimize route, Update job notes, Attach job photo, List estimates, Create estimate, Edit estimate, Send estimate, List invoices, Create invoice, Edit invoice, Send invoice, Record payment, Get payment link, Export invoices, Get receivables report, Configure invoice reminders, List crew, Manage team member, Invite team member, List activity, Manage message template, Configure online booking, Set default tax rate, Pause recurring job, Review team request, Get referral code, Bulk assign jobs, Claim job, Schedule recurring visit, End recurring service, Reorder route, Generate customer portal link, Review booking request, Get dashboard, List recurring services, Get job completion report, Get estimate conversion report, List measurement history, Generate referral code, Configure referral rewards, Download estimate pdf, Remind estimate, List document approvals, Review document approvals, Send payment receipt, List message history, Configure review requests, Update business settings, Configure estimate defaults, Set notification preferences, Remove team member, Regenerate team invitation, Set technician visibility, Transfer business ownership, Get payment setup status, Manage payment connection, Open payout dashboard, Get subscription, Manage subscription, Read customer portal, Pay customer invoice, Respond to estimate, Submit booking request, Confirm job assignment.

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

NameRequiredDescriptionDefault
appNoLeave 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.
urlNoA public http or https address, e.g. https://example.com.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint, openWorldHint, idempotentHint=false), the description adds real context: the browser is a real Chrome session where the user is signed in, tab side effects are minimized, and the call answers with the page's visible elements and text using the same numbering as other tools. It is silent on failure modes and session reuse, which keeps it from a 5.

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 opening sentences are well front-loaded, but the definition then dumps a ~70-item enumeration of CrewNest actions that dominates the text and conveys no callable guidance for this tool. That bulk dilutes the actionable instructions and should be replaced by a short routing rule.

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 two-parameter tool with full schema coverage and no output schema, the description covers the essential facts: when to call it, what session it runs in, how tab targeting works, and what comes back. Nothing an agent needs to invoke it correctly is missing.

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% and the schema already explains both `app` and `url` including the omit-default rule for `app`. The description adds only indirect meaning for `url` via tab-routing behavior and never mentions the `app` escape hatch, so it is baseline-adequate rather than additive.

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?

States a specific verb and resource: it starts the user's Cloud Browser (a real signed-in Chrome) and opens `url`, with a clear entry-point role. It does not distinguish itself from the sibling cotlet_browser_navigate, which on its name alone appears to also load a URL, so it stops short of a 5.

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 relative to the other browser tools, and it clarifies tab behavior (existing site tab, else new tab, user's tabs preserved). It offers no when-not guidance and never says how it relates to cotlet_browser_navigate, so the alternative-selection story is incomplete.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources