CoachingPortal by Cotlet

Send message in CoachingPortal

coachingportal_send_message

Read-onlyIdempotent

Send message 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_send_message"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A4/5.0

Behavior4/5

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

Adds real context beyond the annotations: it discloses that the return value is a UI walkthrough (screens, buttons, fields) and that the tool has no side effects, which reconciles the misleading 'send' name with readOnlyHint=true. It also explains the architectural reason (no public CoachingPortal API) for the browser hand-off. Auth requirements and step granularity limits are not covered.

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?

Three sentences, each carrying information: what it does, what it returns, and what to do next. The 'from ChatGPT, Claude or any AI agent' phrase is mildly decorative, and the API note would land better adjacent to the browser-tools sentence, but nothing is padded.

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 input schema and no output schema, the description carries the full burden and mostly meets it: it names the return shape and the follow-up tool family. The one gap is how the actual message content and recipient enter the flow, which an agent must infer.

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 4 baseline applies. It could have been clearer that the message text and recipient are supplied later through the browser tools, since an agent may expect to pass them here.

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 ('Send message in the user's own CoachingPortal account') and immediately qualifies the surprising part: the tool returns step-by-step instructions rather than performing the send. It does not distinguish itself from the close sibling coachingportal_send_voice_message, so an agent choosing between message modalities gets no help here.

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: get the steps from this tool, then execute them with the cotlet_browser_* tools in the user's Cloud Browser, and it plainly rules out any direct effect ('opens nothing by itself'). No guidance on when to prefer the voice-message sibling or on preconditions such as being logged in to CoachingPortal.

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?