CoachingPortal by Cotlet

Configure check in questions in CoachingPortal

coachingportal_configure_check_in_questions

Read-onlyIdempotent

Configure check in questions 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_configure_check_in_questions"
  }
}

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, destructiveHint=false and idempotentHint=true, and the description reinforces this by stating it opens nothing by itself and performs no changes. It also discloses the practical constraint that there is no public CoachingPortal API and that execution must go through the browser tools — real behavioral context beyond the annotations.

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?

Front-loaded with the purpose, then the return behavior, then the follow-up mechanism. Every clause carries information, though the single long sentence chain and the mid-sentence '(screens, buttons, fields)' insertion make it slightly dense.

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, no-output-schema tool, the description covers what is returned (step-by-step screens, buttons, fields), that nothing is executed, and how to complete the action afterward. Enough for an agent to call it correctly and route the follow-up.

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 (schema coverage 100%), so there is nothing for the description to disambiguate. Baseline 4 applies; the description correctly avoids inventing parameter detail.

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?

States a specific verb and resource: configuring check-in questions in the user's own CoachingPortal account, from any AI agent. It clearly distinguishes that this tool returns instructions rather than performing the change, which separates it from action-oriented siblings like coachingportal_respond_to_check_in or coachingportal_list_check_ins, though it never names a sibling explicitly.

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?

Gives concrete usage context: call it to learn the steps, then execute with cotlet_browser_* tools in the CoachingPortal Cloud Browser. It explains the handoff well but offers no explicit exclusions or comparison to the other check-in configuration/response 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?