sevdesk MCP Server and API by Cotlet

Cotlet: how to work in an app

cotlet_app_guide

Read-onlyIdempotent

How to work in an app by clicking in the user's Cloud Browser with Cotlet's browser tools: which browser to use for this workspace and the sign-in link, the method step by step, the app's screens, menus and actions, notes, and the app's dedicated tools when Cotlet has them. Call it before the first browser step in an app. Works for any web app; one outside Cotlet's catalog gets the general method. Free, no browser session. For sevdesk it covers 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_app_guide"
  }
}

Input Schema

Name	Required	Description	Default
`app`	No	The app's name or Cotlet slug. Default: sevdesk.
`task`	No	What the user wants done in the app, in their words.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, not open-world), and the description adds genuinely new behavioral context: 'Free, no browser session,' which tells the agent this call costs nothing and does not open or occupy the Cloud Browser. It also enumerates the kinds of content returned, which annotations cannot convey. It does not discuss result size or caching, but the added value is real.

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 core routing instruction ('Call it before the first browser step') lands early, and the closing sevdesk action list is useful scoping information rather than filler. The opening sentence is a dense, comma-heavy list that takes effort to parse, which is the main deduction.

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, so the description carries the burden of describing return content, and it does so by enumerating browser choice, sign-in link, method steps, UI map, notes, and dedicated tools. Combined with the 'free, no browser session' cost note, an agent has enough to decide and invoke correctly; only the shape/format of the returned guidance is left vague.

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 optional parameters (app, task) are already documented in the schema, including the sevdesk default. The description reinforces this with 'For sevdesk it covers these actions: ...' but adds no syntax, format, or fallback behavior beyond what the schema states. Baseline 3 is appropriate.

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 names the resource precisely: a per-app working guide covering which browser to use, the sign-in link, the step-by-step method, screens/menus/actions, and the app's dedicated tools. That is far more specific than the title, and it implicitly distinguishes itself from the browser_* action siblings by being the pre-step reference. It stops short of a crisp one-line 'returns guidance for X' framing, which keeps it out of 5 territory.

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?

Timing is stated explicitly: 'Call it before the first browser step in an app,' which is the key routing decision versus cotlet_browser_* tools. It also clarifies scope ('works for any web app; one outside Cotlet's catalog gets the general method'), so an agent knows it is not limited to catalogued apps. No explicit when-not or named alternative tool is given, so it is not a full 5.

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?