CoachingPortal by Cotlet

Manage pt session in CoachingPortal

coachingportal_manage_pt_session

Read-onlyIdempotent

Manage pt session 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_manage_pt_session"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A4.2/5.0

Behavior5/5

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

The description adds substantial behavioral context beyond the annotations: it explains that the tool only returns instructions with screens, buttons, and fields, opens nothing by itself, and must be followed by cotlet_browser_* actions. It also notes that CoachingPortal has no public API, which clarifies why a browser-based follow-up is required.

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?

The description is compact and mostly front-loaded, with the key clarification that the tool returns instructions and performs no action. The opening 'Manage pt session' is slightly misleading before the clarification arrives, and the note about no public API is useful but could be tightened.

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 tool with annotations covering read-only and non-destructive behavior, the description is largely complete: it explains the return behavior, confirms no side effects, and routes execution to browser tools. It leaves some ambiguity about which PT-session operations 'manage' covers, but nothing essential for invoking the tool correctly 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?

There are zero input parameters, so the description has no parameter semantics to add. The baseline score for a parameterless tool is 4, and nothing in the description misrepresents the empty schema.

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 clearly states that this tool returns step-by-step instructions for managing a PT session rather than performing the action: 'Returns how to do it in CoachingPortal step by step (screens, buttons, fields) and opens nothing by itself.' However, 'Manage pt session' is broad and does not distinguish this tool from siblings such as list_pt_sessions or log_pt_workout, so the agent must infer the correct scope.

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?

The description gives a clear workflow: call this tool to get step-by-step instructions, then execute the steps with the cotlet_browser_* tools. It does not explicitly state when not to use this tool or name alternative CoachingPortal siblings, but the intended usage context is clear.

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?