Okendo 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 Okendo it serves these actions: List pending reviews, Publish review, Reject review, Reply to review, Answer product question, Get product performance.

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

A3.7/5.0

Behavior4/5

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

Annotations cover safety (readOnlyHint, destructiveHint=false, openWorldHint) and non-idempotence, and the description adds genuine context beyond them: the session is the user's own signed-in Chrome, the URL reuses the site's existing tab or opens a new one so the user's tabs survive, and it returns the visible page with the same element numbering used elsewhere. It does not explain why the call is non-idempotent or what happens on failure, which keeps it short of 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.

Conciseness4/5

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

Front-loaded with the action and the ordering instruction, then tab behavior, then the return value — a sensible progression with little waste. The final sentence enumerating Okendo actions is the one part that does not clearly earn its place and could mislead an agent into thinking the tool is Okendo-specific.

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?

There is no output schema, and the description compensates by describing what comes back (elements and text in view with the same numbering), plus the tab-reuse side effect and the sequencing requirement. Given a two-parameter, low-complexity tool, the only real omission is any guidance versus cotlet_browser_navigate.

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 both parameters are documented in-schema, including the unusual 'leave app out' default, so the baseline is 3. The description corroborates the default and explains where the URL lands (existing site tab vs new tab), but adds no syntax or format detail beyond the schema.

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: starts the user's Cloud Browser (real Chrome, signed in) and opens `url`, plus 'Call it first' establishing ordering. It is distinguishable from most siblings (click, type, scroll), but it never distinguishes itself from cotlet_browser_navigate, which is the obvious confusable, leaving a small ambiguity in the core action.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Call it first' gives real sequencing guidance for the browser tool family, which is useful. However there is no when-not guidance and no named alternative (e.g. navigate for an already-open browser), and the trailing Okendo action list is usage context of unclear relevance rather than a routing rule.

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

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