CoachingPortal by Cotlet

Set notification preferences in CoachingPortal

coachingportal_set_notification_preferences

Read-onlyIdempotent

Set notification preferences 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_set_notification_preferences"
  }
}

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 explains exactly why: the tool 'opens nothing by itself' and only returns a procedure, so the read-only annotation is coherent rather than contradictory. It adds useful context beyond annotations by describing the return content (screens, buttons, fields) and by explaining that CoachingPortal publishes no public API, which justifies the browser-based follow-up. It does not mention auth, permissions, or rate limits, but the safety profile is well 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, front-loaded with what the tool does and immediately followed by the crucial caveat that it performs no action. The closing API sentence is slightly awkward ('official API: ... publishes no public API') but earns its place by explaining the browser-automation requirement.

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?

There is no output schema, so the description carries the burden of describing the return value, and it does: a step-by-step guide with screens, buttons, and fields. It also supplies the essential next step (cotlet_browser_* tools) and the reason no direct API call exists. Complete enough for an agent to call and act on the result correctly.

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; the baseline for a parameterless tool applies. No misleading parameter language is present.

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 ('Set notification preferences in the user's own CoachingPortal account') with an explicit scope restriction to the caller's own account. It also corrects the misleading name by clarifying the tool returns step-by-step guidance rather than performing the change. It does not explicitly distinguish itself from any sibling, though no sibling in the listed set covers notifications.

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 a clear usage path: call this to get the procedure, then execute it with the cotlet_browser_* tools in the user's Cloud Browser. It also frames the audience ('from ChatGPT, Claude or any AI agent'). It stops short of stating when NOT to use it or naming a competing 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?