TotalCoaching by Cotlet

Read client profile in TotalCoaching

totalcoaching_read_client_profile

Read-onlyIdempotent

Read client profile in the user's own TotalCoaching account from ChatGPT, Claude or any AI agent. Returns how to do it in TotalCoaching step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's TotalCoaching Cloud Browser. TotalCoaching's official API: TotalCoaching does not publish a general-purpose record-management API reference in the vendor sources checked on 12 November 2026.

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": "totalcoaching_read_client_profile"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the tool opens nothing by itself and returns procedural content (screens, buttons, fields) rather than data, which is the key surprise an agent needs to know.

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 core behavior and the follow-on browser-tool instruction are front-loaded and clear. However, the trailing sentence about TotalCoaching not publishing a general-purpose API reference (dated 12 November 2026) is tangential noise that does not help an agent decide or invoke, and it dilutes an otherwise tight definition.

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 no parameters, no output schema, and strong annotations, the description covers what an agent needs: what comes back (step-by-step guidance) and what to do next. A brief note on the shape or granularity of the returned steps would make it fully self-sufficient.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate. Baseline 4 applies; the description correctly implies no inputs are needed.

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 states a specific behavior: it returns step-by-step instructions (screens, buttons, fields) for reading a client profile in TotalCoaching, rather than reading the record itself. This corrects the potentially misleading name and separates it from the cotlet_browser_* tools that perform the action. It stops short of differentiating against the other totalcoaching_* sibling 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 workflow context: call this first to get instructions, then execute them with cotlet_browser_* tools in the Cloud Browser. It does not state when not to use it, nor how it relates to other TotalCoaching guide/read tools, so no explicit exclusions are present.

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?