Squire 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 Squire it serves these actions: List appointments, Book appointment, Reschedule appointment, Cancel appointment, List waitlist, Block time off, List clients, Get revenue report.

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

Behavior4/5

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

Beyond the annotations it discloses the important behavioral facts: the browser is a real signed-in Chrome session (auth context), the target tab is the site's existing tab else a new one so the user's tabs are preserved, and the call answers with the page's in-view elements and text. The one omission is whether calling when a browser is already open starts a second one — notable since idempotentHint is false.

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

Conciseness3/5

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

The opening is well front-loaded — purpose, ordering, tab behavior, then return shape. But the closing enumeration of eight Squire actions (List appointments, Book appointment, ...) is an operational catalog unrelated to opening a URL and dilutes the description; that list belongs with the squire_* tools.

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 correctly carries the return-value burden by describing the elements and text returned and their numbering. Two fully-documented parameters plus auth and tab semantics make it near-complete; only the already-running-browser case is unaddressed.

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 parameters are already documented, which sets the baseline at 3. The description adds only the routing behavior of `url` (existing tab vs new tab) and says nothing about the `app` parameter's slug semantics, so it does not meaningfully exceed the schema.

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: it starts the user's Cloud Browser (a real Chrome where the user is signed in) and opens `url`. The phrase 'Call it first' also positions it as the entry point relative to the other browser_* tools, so an agent can tell what this does without opening the schema.

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 ordering guidance against every sibling page-action tool, and the tab-fallback sentence tells the agent it does not need a separate tab-management call. It does not say what happens if the browser is already running, nor does it name any sibling it should be swapped for, so it falls short of full when/when-not coverage.

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

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