Skip to main content
Glama
Sign In

Paired Plus by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

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 Paired Plus it serves these actions: List appointments, Create appointment, Reschedule appointment, Create group booking, List waitlist, Set service pricing, Set booking rules, List clients, Add client note, Save color formula, Set client service time, Send client form, List client forms, Manage standing appointment, List inventory, Manage product, Update stock count, Create purchase order, Receive purchase order, Get inventory report, List sales, Checkout sale, Redeem gift card, Sell membership, Sell service series, Redeem rewards, Configure promotion, Get gift card balances, Sell gift card, List marketing audience, Send email campaign, Configure email follow up, Get campaign report, Get sales insights, Charge card on file, Collect booking deposit, Prepare email campaign, Manage service provider, Manage service, Set staff schedule, Manage booking resources, Create client form, Update client form response, Set client tracking fields, Create product kit, List open purchase orders, Close register, Refund sale, Configure service series, Redeem service series, Configure membership rewards, Create payment type, Apply account payment, Configure card and cancellation policy, Store client payment method, Export marketing list, Send text campaign, List conversations, Send text message, Configure darci automation, Configure product purchase reminder, Configure online promotion, Set gift card amounts, Set shipping fees, Publish last minute booking, Add appointment add on, Cancel appointment, Switch calendar provider, Set calendar preferences, Get business reports, Build custom report, Forecast revenue, Get payroll commissions, Lookup hotel guest, Post room charge, Issue room credit, Reconcile pms night audit, Set interface labels, List online services, Book online appointment, List personal appointments, Buy online gift certificate, Buy online retail, Manage user permissions.

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?

Annotations already declare readOnly, non-destructive, open-world and non-idempotent, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the browser is a real signed-in Chrome instance, opening a URL may reuse an existing tab rather than create a new one, and the tool answers with the page's visible elements and text. It does not discuss failure modes such as an unreachable URL.

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 first three sentences are tight and front-loaded, but they are followed by a roughly ninety-item enumeration of Paired Plus actions that has no bearing on selecting or invoking this browser-opening tool. That dump dominates the description's length and buries the operative 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?

For a two-parameter, fully documented, non-destructive tool with no output schema, the core description covers what it does, when to call it, tab behavior, and what comes back. The only shortfall is that the trailing action catalog adds bulk without adding completeness.

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 baseline is 3, and the description adds real meaning on top: the `url` is routed to the site's existing open tab when one exists, and the `app` parameter is implicitly the exception path since the default is the user's own browser. That is more than the schema states on its own.

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 gives a specific verb and resource: it starts the user's Cloud Browser (real Chrome, signed-in session) and opens `url`, and it explicitly says to call it first. It is clear about what the tool does, though it never contrasts itself with the sibling `cotlet_browser_navigate`, which an agent could plausibly confuse it with.

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" is a direct sequencing instruction, and the tab-targeting rule (reuse the site's open tab, otherwise a new tab, never disturbing the user's tabs) tells the agent what to expect. There is no explicit when-not guidance and no mention of when `cotlet_browser_navigate` should be used instead.

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

All Paired Plus by Cotlet toolsInspect
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