Skip to main content
Glama
Sign In

tl;dv MCP Server and API 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 tl;dv it serves these actions: List meetings, Get transcript, Create clip, Add note, Share meeting, Add meeting to folder.

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

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, and the description adds real context beyond them: the browser is the user's signed-in Chrome, existing user tabs are preserved, and the answer returns the viewed elements and text with matching numbers. Return behavior is described even though no output schema exists. It does not cover failure cases such as popups blocking or a site being slow.

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 ordering rule in the first two sentences, with no filler. The trailing tl;dv action list is useful for routing but is a shotgun enumeration that lengthens the definition without adding invocation mechanics.

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?

Covers what the tool does, when to call it, where the URL lands, and what comes back, which is sufficient for a two-parameter, non-destructive open action with no output schema. Only edge-case behavior and the app-use case are left to the schema.

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 meaning about `url` that the schema lacks: it goes to the site's open tab when one exists, otherwise a new tab. The `app` parameter is only explained by the schema, not the description.

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: starts the user's Cloud Browser (a real Chrome on Cotlet) and opens `url`, plus a clear ordering rule, 'Call it first.' It does not explicitly name the nearby sibling cotlet_browser_navigate, so the open-vs-navigate distinction is only implied by ordering.

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 an explicit when-to-use rule that an agent can act on without opening the schema. It also explains the tab-targeting behavior that decides where the URL lands. There is no when-not-to-use statement or named alternative for subsequent navigation.

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

All tl;dv MCP Server and API 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