CoachingPortal by Cotlet

Add resource in CoachingPortal

coachingportal_add_resource

Read-onlyIdempotent

Add resource 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_resource"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A3.8/5.0

Behavior4/5

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

The description resolves the tension between the 'add' name and readOnlyHint=true by explicitly saying it 'opens nothing by itself' and only returns instructions. It also adds non-annotation context (no public CoachingPortal API, execution happens in a separate Cloud Browser). It does not state prerequisites such as whether the browser session must be connected or the user authenticated.

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 behavior and the no-side-effect guarantee are front-loaded in the first two sentences. The closing clause 'CoachingPortal's official API: CoachingPortal publishes no public API' is slightly redundant phrasing, but it is short and adds the API-absence context.

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 tool with no output schema, the description covers what is returned (step-by-step screens/buttons/fields) and how execution follows. Missing only edge-case context: what happens if no Cloud Browser session exists and whether the user must confirm before the agent drives the browser.

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 no parameter semantics to explain and the baseline of 4 applies. The description correctly implies nothing is passed in — the target resource must be inferred from the conversation.

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 names a specific verb and resource (add a resource to the user's own CoachingPortal account) and clarifies the actual deliverable: step-by-step instructions with screens, buttons and fields. It does not distinguish itself from the many coachingportal_* siblings, but an agent can tell it is a guidance tool rather than an executor.

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 states the usage context ('from ChatGPT, Claude or any AI agent') and gives a clear two-step workflow: call this for instructions, then execute with cotlet_browser_* tools in the Cloud Browser. It offers no when-not guidance and no comparison to sibling tools such as coachingportal_attach_client_resource, so selection among siblings is left to inference.

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?