CoachingPortal by Cotlet

Open pt join code in CoachingPortal

coachingportal_open_pt_join_code

Read-onlyIdempotent

Open pt join code 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_open_pt_join_code"
  }
}

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, idempotentHint=true and destructiveHint=false, and the description reinforces this with the important clarification that it 'opens nothing by itself' and only returns guidance. It also discloses the no-public-API constraint that explains why this indirection exists, adding genuine context beyond the annotations, though it does not say how account-specific or formatted the returned steps are.

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 the core action and the key non-action caveat. The 'from ChatGPT, Claude or any AI agent' clause and the oddly phrased 'CoachingPortal's official API: CoachingPortal publishes no public API' add some noise, but nothing is buried or wasted.

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 parameters and no output schema, the description carries the burden of explaining what comes back, and it does so ('how to do it in CoachingPortal step by step (screens, buttons, fields)'). Combined with the annotation profile, an agent has enough to select and call it correctly; only the exact return structure is 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 nothing for the description to disambiguate. The definition correctly spends no words on parameter semantics, matching the baseline for a 0-param tool.

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 action and resource (open the PT join code in the user's own CoachingPortal account) and explicitly defines the deliverable as step-by-step instructions rather than the action itself. That distinguishes it from the cotlet_browser_* tools that actually perform the navigation, though the phrase 'pt join code' remains jargon-heavy.

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 states the context of use (user's own account, no public CoachingPortal API exists, so this is the only route) and names the follow-up alternative: 'then do it with the cotlet_browser_* tools in the user's CoachingPortal Cloud Browser.' No explicit when-not-to-use case is given, which keeps it short of a 5.

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?