ClubReady 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 ClubReady it covers these actions: Search customer or prospect profiles, View a customer profile, View customer amenities.

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: ClubReady.
`task`	No	What the user wants done in the app, in their words.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety bar is lower; the description still adds real behavioral context by clarifying it is free and opens no browser session, and by describing the kind of content returned (browser choice, sign-in link, per-screen actions). It does not state how large the response is or whether it is cacheable, but that is minor 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.

Conciseness3/5

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

The purpose is front-loaded, but the opening sentence is a run-on with six colon-separated clauses that could be pruned. The trailing ClubReady action enumeration consumes notable length for a single-catalog example. Still, no sentence is pure filler.

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 two-optional-parameter, read-only guide with full schema coverage and no output schema, the description supplies what an agent needs: when to call it, that it costs no browser session, and roughly what comes back. It stops short of describing response structure or how to apply the returned method, which would have completed the picture.

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% for both parameters (app, task), so the schema carries the semantics. The description adds only indirect value via the 'Works for any web app; one outside Cotlet's catalog gets the general method' note, which hints that `app` tolerates unknown names, and the ClubReady action list hints at valid `app` values. That is marginal beyond 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 names the resource precisely: a look-up guide for operating an app inside the Cloud Browser, and enumerates what it returns (which browser, sign-in link, step-by-step method, screens/menus/actions, dedicated tools). It is distinguishable from the cotlet_browser_* siblings by the explicit 'Free, no browser session' note. The long colon-delimited enumeration of contents blurs the core purpose slightly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit trigger ('Call it before the first browser step in an app') plus exclusions ('Free, no browser session' — so it does not substitute for the browser tools). It also states coverage scope: any web app works, and apps outside the catalog fall back to a general method, with a named example of action coverage for ClubReady.

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

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