TotalCoaching 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 TotalCoaching it covers these actions: List clients and activation status, Read client profile, Read client training calendar.

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: TotalCoaching.
`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.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 adds value beyond them by stating 'Free, no browser session' (no cost, no session is opened) and by enumerating the kind of content returned. It does not describe return formatting or how much content to expect, so it stops short of full disclosure.

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 purpose and the 'call before the first browser step' directive are front-loaded, and the closing example list anchors the abstract description. The first sentence is a long comma-chained enumeration that is denser than necessary, but no sentence is padding.

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 must convey what comes back, and it does via the enumerated contents (browser choice, sign-in link, method, screens, notes, dedicated tools). With only two well-documented optional parameters, the remaining gap is minor detail about guide length or app-name mismatch handling.

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% and both parameters carry descriptions plus a stated default (TotalCoaching), so the schema does the baseline work. The description adds meaning to the `task` parameter by listing concrete example actions for TotalCoaching (list clients and activation status, read client profile, read client training calendar), showing the granularity of task phrasing expected.

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 names a specific resource (an app-operating guide) and enumerates its contents: which browser to use for the workspace, the sign-in link, the step-by-step method, screens/menus/actions, notes, and the app's dedicated tools. 'Free, no browser session' clarifies that it is a reference lookup rather than an action tool, which separates it cleanly from the many cotlet_browser_* siblings.

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 trigger condition tied to the browser workflow. It also notes that apps outside Cotlet's catalog receive the general method and that dedicated tools exist when available, which implies routing. No explicit when-not-to-call or named alternative is given, keeping 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.

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