CoachingPortal by Cotlet

Update coach profile in CoachingPortal

coachingportal_update_coach_profile

Read-onlyIdempotent

Update coach 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_coach_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?

Adds substantial context beyond the annotations: the name says 'update' and readOnlyHint=true, and the description resolves that by explicitly saying it 'opens nothing by itself' and only returns screens/buttons/fields to follow. That pre-empts a likely misread of the tool. It does not cover prerequisites such as whether the user must already be signed in to the Cloud Browser.

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 purpose and the 'returns instructions, opens nothing' constraint are front-loaded and the whole definition is three sentences. However, 'CoachingPortal's official API: CoachingPortal publishes no public API' is a redundant restatement, and the repeated product name adds noise.

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?

No output schema exists, and the description does explain the return value (step-by-step screens, buttons, fields), which is the key thing an agent needs. For a zero-parameter instruction tool the coverage is close to complete, with only authentication/session prerequisites left implicit.

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 no parameter meaning to clarify and the schema carries no burden. The description correctly implies the target profile is implicit (the user's own account) rather than configurable.

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 (update coach profile) and scopes it to the user's own CoachingPortal account, plus clarifies the tool returns step-by-step UI instructions rather than performing the write. It does not explicitly differentiate from near-siblings like update_personal_profile or update_client_profile_metrics, so an agent must infer which profile type applies.

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?

Gives clear usage context: call this to get instructions, then perform the actual change with cotlet_browser_* tools in the CoachingPortal Cloud Browser. It also notes CoachingPortal has no public API, which explains why this indirect route exists. It stops short of stating when this is the wrong choice versus the personal-profile sibling.

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?