Skip to main content
Glama

Bookipi 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 Bookipi it serves these actions: Filter invoice lists and view archived invoices, Review customer correspondence and transaction history, View or download an eSign audit trail.

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.9/5.0
Behavior4/5

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

Adds real behavior beyond the annotations: a genuine signed-in Chrome, URL routed to the site's existing tab or a new tab so the user's own tabs survive, and the page state returned (visible elements and text with matching numbers). This meaningfully informs an agent about side effects and follow-up reading on a tool with no output schema. It omits what happens when `url` is left out, even though the schema marks it optional.

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?

Front-loaded with the core action and the ordering instruction, then behavior, then use cases. The trailing sentence enumerating Bookipi actions is somewhat boilerplate and long, but it does earn its place as routing context for the app-specific siblings.

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 open/browse tool with annotations and no output schema, the description covers ordering, side effects on the user's tabs, and what the agent receives afterward. The remaining gap is the optional-`url` case, which is neither in the description nor resolved by the annotations.

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, including the 'leave it out' guidance for `app`. The description only adds tab-targeting meaning for `url` ('goes to the site's open tab, else to a new tab') and says nothing about `app` beyond what the schema states, so the baseline of 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?

States a concrete verb and resource: it starts the user's Cloud Browser and opens a `url` in a real Chrome session. 'Call it first' signals it is the entry point relative to the many other cotlet_browser_* action tools, though it never names `cotlet_browser_navigate` outright, so the boundary with that sibling is left 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 clear ordering guidance, and the app parameter text says when to omit it (the default browser session) versus when to supply a slug that `cotlet_app_guide` named. It also lists the Bookipi actions it enables, which frames the use case. It stops short of stating when not to call it, e.g. when a session is already open and 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.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources