CoachingPortal by Cotlet

Get coach referrals in CoachingPortal

coachingportal_get_coach_referrals

Read-onlyIdempotent

Get coach referrals 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_get_coach_referrals"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already cover read-only, non-destructive, idempotent, and closed-world, so the bar is lower, but the description adds real value: it discloses that the response is a step-by-step walkthrough of screens/buttons/fields and that it 'opens nothing by itself' as a side-effect guarantee. The absence of an output schema makes that output-shape disclosure especially useful.

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 important content is front-loaded, but the phrasing is loose: 'from ChatGPT, Claude or any AI agent' is filler, and 'CoachingPortal's official API: CoachingPortal publishes no public API' is an awkward, semi-redundant construction. The sentences are semicolon-chained and could be tightened without losing meaning.

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 zero-parameter tool with full annotation coverage and no output schema, the description supplies what an agent needs: what comes back (a step-by-step guide), what it does not do (opens nothing), and how to act on the result (browser tools). The only gap is not naming a specific browser tool to use next.

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 and the baseline of 4 applies. No parameter-level information is missing.

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 a specific resource (coach referrals) and, crucially, discloses that the tool 'Returns how to do it in CoachingPortal step by step (screens, buttons, fields) and opens nothing by itself,' which reframes it from a data-fetch into an instructions-retrieval tool. The opening verb 'Get' is slightly at odds with that clarification, but the second sentence resolves the ambiguity well enough to distinguish it from data-returning siblings like coachingportal_get_client_progress.

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 explicitly states the follow-up path ('then do it with the cotlet_browser_* tools in the user's CoachingPortal Cloud Browser') and rules out the API route ('CoachingPortal publishes no public API'), which is strong routing guidance. It stops short of naming when NOT to use it or which specific cotlet_browser_* tool to call first, leaving some inference.

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?