CoachingPortal by Cotlet

Update client profile metrics in CoachingPortal

coachingportal_update_client_profile_metrics

Read-onlyIdempotent

Update client profile metrics 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_client_profile_metrics"
  }
}

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 declare readOnlyHint=true and destructiveHint=false, and the description reinforces this ("opens nothing by itself"). It adds genuine context beyond annotations: the return shape (step-by-step screens/buttons/fields), the follow-up browser-tool workflow, and the absence of a public API. No contradiction with readOnly; the disclosure is useful and non-redundant.

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 compact sentences, front-loaded with purpose then the follow-up action. Minor filler ("from ChatGPT, Claude or any AI agent") crowds an otherwise tight, earned description.

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, instruction-returning tool with rich annotations and no output schema, the description covers what it returns, that it takes no action, and how to complete the task. Enough for an agent to call it correctly and route to the browser tools afterward.

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 has zero parameters, so the schema baseline is 4 and there is no parameter meaning to add. Nothing is missing on this dimension.

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+resource ("Update client profile metrics") and then clarifies the real behavior: it returns step-by-step CoachingPortal instructions (screens, buttons, fields) rather than performing the update. This distinguishes it from siblings like update_coach_profile and update_personal_profile by the 'metrics' scope, though the name's 'update' verb is slightly at odds with the instruction-returning behavior until the body explains it.

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 when-to-use context: call this to get the walkthrough, then execute with cotlet_browser_* tools in the Cloud Browser. It also rules out the API path ("publishes no public API"). It stops short of explicit when-not-to-use exclusions, but the follow-up path is well specified.

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?