CoachingPortal by Cotlet

Update personal profile in CoachingPortal

coachingportal_update_personal_profile

Read-onlyIdempotent

Update personal profile 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_update_personal_profile"
  }
}

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?

Annotations already mark this readOnly and non-destructive; the description reinforces that by stating it 'opens nothing by itself' and returns screens, buttons and fields. That is meaningful disclosure of a two-step guidance pattern, though it says nothing about authentication state or what happens if the agent skips the browser step.

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 core behavior (returns steps, does not act) is front-loaded in the first sentence, with the follow-up action and API note after. The trailing 'official API: CoachingPortal publishes no public API' phrasing is slightly redundant but earns its place by killing the API assumption.

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, no-output-schema tool, the description covers what comes back (screens, buttons, fields) and the required follow-up path. It could add a note on prerequisites such as the user being signed in to the Cloud Browser session, but nothing essential is omitted.

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 the baseline is 4 and there is nothing the description needs to disambiguate. The absence of parameters is itself consistent with a pure guidance call.

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 verb and resource (update personal profile) and scopes it to the user's own account, which separates it from the coach/client profile siblings. It also clarifies the tool's real output is step-by-step instructions rather than the mutation itself.

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 routes the agent: call this to get the click-by-click steps, then perform the change with the cotlet_browser_* tools in the Cloud Browser, and notes there is no public API to fall back on. What's missing is guidance on when to prefer this over the sibling profile-update tools (coach vs. client vs. personal).

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?