sevdesk 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 sevdesk it serves these actions: Create invoice, Send invoice, Upload receipt, Book voucher, List open invoices.

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, the description explains that this is a real Chrome where the user is signed in, that the URL goes to the site's open tab or a new tab to preserve the user's tabs, and that it returns the page's visible elements and text. This is substantial behavioral context, though it does not address the non-idempotent hint or discuss error/auth-expiry behavior.

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?

The description is front-loaded with the core action and the 'Call it first' instruction. It is mostly efficient, but the sevdesk action list and the vague phrase 'with the same numbers' add some noise without adding full clarity.

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?

The description covers the start action, URL tab behavior, and return content, which is important because there is no output schema. It is nearly complete for a browser-open tool, though the return phrasing 'the same numbers' is somewhat ambiguous and could be clearer.

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. The description adds useful semantics for `url` by explaining that it goes to the site's open tab or otherwise a new tab, which is meaning beyond the schema's format description; the `app` parameter is left to 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?

The description states a specific verb and resource: it starts the user's Cloud Browser and opens `url`. It is clear what the tool does and 'Call it first' indicates sequencing, but it does not explicitly distinguish itself from the sibling `cotlet_browser_navigate`.

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?

The instruction 'Call it first' gives clear when-to-use guidance for starting browser workflows. However, it does not name or exclude alternatives such as `cotlet_browser_navigate`, so an agent must infer the boundary from context.

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

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