Skip to main content
Glama

Pabau 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 Pabau it covers these actions: View appointments and navigate calendar dates and Day/Week/Month views, Filter the calendar by locations, employees/teams, statuses and services, Hide client details on the calendar display.

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

NameRequiredDescriptionDefault
appNoThe app's name or Cotlet slug. Default: Pabau.
taskNoWhat the user wants done in the app, in their words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered; the description still earns credit by adding "Free, no browser session" — cost and session side-effect information that the annotations cannot express. It also scopes what Pabau-specific content is included, which helps the agent judge the answer's coverage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The purpose is front-loaded in the opening clause, but the whole definition is delivered as one long run-on sentence with heavy comma-chaining, and the trailing Pabau action inventory duplicates ground already covered by dedicated sibling tools. Readable, but not tight.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and only two optional parameters, the description carries the burden of describing returns, and it does: browser choice, sign-in link, method, screens/menus/actions, notes, and app-specific tools. An agent knows what it will get back and when to call it, with no material gap.

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 the schema lacks: the app argument accepts any web app or a Cotlet slug, and apps outside the catalog still get the general method. The bundled Pabau action list further signals the granularity the app/task inputs resolve to.

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?

States a specific resource (a per-app playbook delivered through Cotlet's Cloud Browser) and enumerates exactly what it contains: browser choice, sign-in link, step-by-step method, screens/menus/actions, notes, and dedicated tools. It is clearly distinguishable from the primitive siblings like cotlet_browser_click or cotlet_browser_navigate, which it references as the tools it prepares the agent to use.

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 before the first browser step in an app" gives an explicit, actionable trigger, and "Works for any web app; one outside Cotlet's catalog gets the general method" sets the fallback expectation. It does not state when the tool is unnecessary (e.g., non-browser tasks) or name a competing alternative, which keeps it short of a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources