CoachingPortal by Cotlet

Get subscription in CoachingPortal

coachingportal_get_subscription

Read-onlyIdempotent

Get subscription 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_subscription"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

B3.3/5.0

Behavior4/5

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

Beyond the readOnlyHint/idempotent annotations, the description discloses that the tool 'opens nothing by itself', that the return payload is step-by-step UI instructions, and that no official public API exists. Those three facts materially shape how an agent should consume the result and sequence the browser tools.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The load-bearing facts are front-loaded, but 'from ChatGPT, Claude or any AI agent' is padding and the closing 'CoachingPortal's official API: CoachingPortal publishes no public API' is redundantly worded and repeats the product name inside one sentence. Tightening would make the when-to-use point land faster.

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, no output schema, and read-only annotations, the main risk is an agent not knowing what comes back — and the description covers that (step-by-step screens, buttons, fields) plus the sequencing into browser tools. The unresolved overlap with manage_subscription is the remaining hole.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There are zero parameters, so the baseline is 4, but the description adds no parameter framing at all (e.g., that the account is implicit from session context). Nothing is wrong here; it simply contributes nothing on this dimension.

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/title read as data retrieval ('Get subscription'), but the body says it 'Returns how to do it in CoachingPortal step by step (screens, buttons, fields)' — a procedure, not subscription data. That clarifies intent only after the reader gets past the misleading opening phrase, and it never distinguishes itself from the sibling coachingportal_manage_subscription.

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 gives a usage context (subscription in the user's own account) and an explicit follow-up path ('then do it with the cotlet_browser_* tools'), which is genuinely actionable. It offers no when-not guidance and never mentions the sibling manage_subscription tool that an agent would plausibly consider as the alternative.

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?