CoachingPortal by Cotlet

List clients in CoachingPortal

coachingportal_list_clients

Read-onlyIdempotent

List clients in the user's own CoachingPortal account from ChatGPT, Claude or any AI agent. Returns how to do it in CoachingPortal step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's CoachingPortal Cloud Browser. CoachingPortal's official API: CoachingPortal publishes no public API.

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Going well beyond the readOnly/idempotent/non-destructive annotations, it discloses the unusual behavior an agent would otherwise get wrong: the tool 'opens nothing by itself' and returns procedural steps (screens, buttons, fields) instead of client records. It also states no public API exists, explaining why the browser path is required. This is exactly the behavioral context annotations cannot convey.

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 scope and the two-step workflow are front-loaded in the first two clauses, which is the right ordering. The trailing 'CoachingPortal's official API: CoachingPortal publishes no public API.' is redundantly phrased and could be one tighter clause, and the sentence overall is a long run-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 no output schema, the description correctly takes on the job of saying what comes back (step-by-step screens, buttons, fields) and what the tool does not do (open anything). What is missing is minor: nothing says whether the returned steps are account-specific or generic, and no note on what to do if the Cloud Browser is not connected.

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 no parameters and the schema is an empty object with additionalProperties false, so there is nothing for the description to disambiguate. Baseline for a zero-parameter tool applies.

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?

States a specific verb and resource ('List clients in the user's own CoachingPortal account') and immediately clarifies the non-obvious twist that it returns step-by-step instructions rather than data. It scopes to the user's own account, which separates it from admin/cross-account siblings, but it never names another coachingportal_* list_* tool to sharpen the distinction.

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?

Explicitly routes the agent to the follow-up action ('then do it with the cotlet_browser_* tools in the user's CoachingPortal Cloud Browser'), which is the critical when-to-use context. It gives no explicit when-not guidance or fallback if the browser tools are unavailable, so it stops short of full routing clarity.

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

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