CoachingPortal by Cotlet

Add progress entry in CoachingPortal

coachingportal_add_progress_entry

Read-onlyIdempotent

Add progress entry 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_add_progress_entry"
  }
}

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

Behavior4/5

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

Annotations declare readOnlyHint=true, and the description reinforces that with 'opens nothing by itself', which resolves the apparent tension between the 'add' verb and the read-only annotation. It also discloses the return nature (step-by-step screens, buttons, fields) and the absence of an official API, though it stops short of showing the exact response format.

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 short and front-loads what matters (it returns steps, it does not act). The closing clause 'CoachingPortal's official API: CoachingPortal publishes no public API' is redundant and slightly clumsy, costing a point.

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 instruction generator with no output schema, the description covers the essential contract: what it returns, that it changes nothing, and which companion tools finish the job. Only the precise response shape is left to discovery, which is a minor gap.

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

Parameters5/5

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

The tool takes zero parameters, and the description explains why: it operates implicitly on 'the user's own CoachingPortal account' with no IDs or selectors required. Nothing about the empty schema is left ambiguous.

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 states a specific verb and resource ('Add progress entry in the user's own CoachingPortal account') and clarifies the crucial twist that it returns instructions rather than performing the action. It does not, however, distinguish this tool from sibling progress tools such as log_personal_progress or create_progress_story, so an agent cannot fully route on name plus description alone.

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?

Usage context is explicit: call from an AI agent, then execute the returned steps with cotlet_browser_* tools in the user's Cloud Browser. What is missing is any when-not guidance or a cue for choosing between this and the sibling progress-logging tools.

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?