CoachingPortal by Cotlet

Get coaching analytics in CoachingPortal

coachingportal_get_coaching_analytics

Read-onlyIdempotent

Get coaching analytics 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_get_coaching_analytics"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A3.6/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the read-only/idempotent/non-destructive annotations, the description adds meaningful behavior: the tool opens nothing by itself, returns procedural screen-level instructions, and there is no public API. These are exactly the traits an agent needs to sequence a browser-driven workflow, though the response format could be more concretely described.

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?

Two sentences that front-load the core action and then the required follow-up with the browser tools. The phrase 'from ChatGPT, Claude or any AI agent' is mild filler, but overall there is little waste.

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 no-parameter, no-output-schema tool, the definition supplies what matters: what it returns (steps with screens/buttons/fields), what it does not do (open anything), and how to continue (cotlet_browser_* tools). Only explicit differentiation from sibling analytics/dashboard tools is missing.

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 are no semantics to explain and the baseline is 4. The description correctly implies no inputs are needed to request the walkthrough.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The name and title say 'get coaching analytics', but the description reveals the tool actually returns step-by-step instructions (screens, buttons, fields) for viewing analytics in CoachingPortal rather than the analytics themselves. That mismatch is clarified in the second sentence, but the definition never distinguishes this from sibling read tools like coachingportal_get_dashboard or coachingportal_get_client_progress, so an agent must infer the boundary.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It clearly states the follow-up pattern: use cotlet_browser_* tools in the CoachingPortal Cloud Browser after getting the steps, and notes that no public API exists (so no API alternative). However, it gives no explicit when-not guidance versus the several other coachingportal_get_* siblings, leaving usage selection implied.

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?