Bizneo 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 Bizneo it covers these actions: List absence requests, Get absence balance, Request absence, Approve absence request, Reject absence request, Request remote work, Approve remote work request, Get my timetable.

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: Bizneo.
`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

A4.1/5.0

Behavior4/5

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

The annotations already establish read-only, idempotent, non-destructive, and non-open-world behavior. The description adds useful behavioral context beyond that by saying the guide is free and uses no browser session, and by explaining what guidance it returns. It does not discuss permissions or rate limits, but those are less critical for a read-only guide.

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 and ordered logically: purpose first, then when to call it, then scope and special cases. The long Bizneo action list is dense but earns its place by clarifying coverage. The overall text is somewhat packed but not padded.

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 simple guide tool with no output schema and full annotation coverage, the description is nearly complete: it explains what is returned, when to call it, and how app coverage works. It could more explicitly connect the listed Bizneo actions to the dedicated bizneo_* tools, but the essentials are present.

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%: the schema already documents the app name/slug, default Bizneo, and the task meaning. The description adds some scope around the app parameter, such as supporting any web app and falling back to a general method outside the catalog, but it does not add format or selection semantics for the task parameter. The baseline of 3 is appropriate when the schema already does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific job: provide guidance for working in an app via the user's Cloud Browser, and it enumerates the returned content (browser/sign-in link, step-by-step method, screens, menus, actions, notes, and dedicated tools). The line 'Call it before the first browser step' clearly distinguishes it from the cotlet_browser_* action tools and the Bizneo action tools.

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?

It gives a clear trigger for use: call it before the first browser step in an app. It also covers scope by saying it works for any web app and that non-catalog apps get the general method. However, it does not explicitly state when not to use it or name alternatives such as cotlet_apps or dedicated Bizneo tools as replacements.

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

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