Skip to main content
Glama
Sign In

Booksy MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

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 Booksy it covers these actions: List bookings, Create booking, Reschedule booking, Reply to review, Read reports.

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: Booksy.
taskNoWhat the user wants done in the app, in their words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the safety profile is covered. The description adds behavior beyond that: it costs nothing ('Free, no browser session'), so no session is opened or consumed, and it discloses the shape of what comes back (method, screens, menus, actions, notes, dedicated tools). It stops short of describing output format or size.

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 operative instruction ('Call it before the first browser step in an app') and the key differentiator ('Free, no browser session') are front-loaded. The long colon-list of contents is dense but each item signals a real capability; the trailing Booksy action list is useful though somewhat tacked on.

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?

With two optional parameters, full schema coverage, annotations, and no output schema, the description covers when to call, what it returns, and how far it generalizes beyond Cotlet's catalog. Only minor gaps remain: no indication of response size/format or what happens for an unrecognized app name.

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%, so both parameters (app name/slug and the task in the user's words) are already documented in the input schema. The description contributes only coverage information — that Booksy is the supported catalog entry with specific actions listed — rather than clarifying parameter usage beyond the schema. Baseline 3 applies.

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 concrete purpose — retrieving a step-by-step operating guide for a given app in the user's Cloud Browser — and enumerates the contents (browser choice, sign-in link, method, screens, menus, actions, notes, dedicated tools). It is clearly separable from the cotlet_browser_* siblings by the line 'Free, no browser session,' which tells the agent this retrieves knowledge rather than driving a browser.

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?

Gives explicit timing: 'Call it before the first browser step in an app,' and extends scope with 'Works for any web app; one outside Cotlet's catalog gets the general method.' It does not name a sibling alternative (e.g., cotlet_apps for enumerating apps) or state a when-not condition, so it falls short of full routing guidance.

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

All Booksy MCP Server and API by Cotlet toolsInspect
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