CoachingPortal by Cotlet

Publish intake form in CoachingPortal

coachingportal_publish_intake_form

Read-onlyIdempotent

Publish intake form 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_publish_intake_form"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Goes well beyond the annotations by disclosing that the tool "opens nothing by itself," that it returns screens/buttons/fields instructions, and that the actual action must happen through cotlet_browser_* in a Cloud Browser. It also explains why that workaround exists ("CoachingPortal publishes no public API"), which is exactly the kind of context annotations cannot convey.

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 key fact — it returns instructions and opens nothing — is front-loaded in the first two sentences. Some phrasing is loose ("from ChatGPT, Claude or any AI agent", the redundant "CoachingPortal's official API: CoachingPortal publishes no public API"), but each sentence still contributes context.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 carries the entire burden and does so: it says what is returned (step-by-step screens, buttons, fields), what is not done (no automatic action), and which tool family completes the job. Nothing an agent needs in order to select and follow up on this tool 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 is nothing for the description to disambiguate and the baseline of 4 applies. The description correctly implies no input is required from the caller.

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+resource ("Publish intake form in the user's own CoachingPortal account") and immediately clarifies the actual mechanic: it returns step-by-step instructions rather than performing the publish. It does not explicitly differentiate itself from the sibling coachingportal_edit_intake_form, so an agent must infer that boundary from the verb 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?

Gives clear usage context: call this to obtain the CoachingPortal procedure, then execute it with the cotlet_browser_* tools in the user's Cloud Browser. It does not state when NOT to use it (e.g., when editing an existing form rather than publishing one), so the exclusions are left implicit.

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?