CoachingPortal MCP Server

coachingportal_open

Opens a CoachingPortal page in your signed-in Cloud Browser so you can review client check-ins and training programs.

Instructions

Open a CoachingPortal page in your signed-in Cloud Browser (default https://app.coachingportal.io) to work with review client check-ins and training programs.

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_open"
  }
}

Input Schema

Name	Required	Description	Default
`url`	No	Page to open. Default: https://app.coachingportal.io

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Nov 12, 2026

TDQS

B3.4/5.0

Behavior3/5

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

With no annotations, the description carries the full burden, and it does contribute the fact that the page loads in a signed-in browser session plus the default destination URL. However, it never states whether navigation replaces the current tab or opens a new one, what happens when the session is unauthenticated, or what the call returns on success or failure.

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?

One sentence with the action front-loaded and no filler. The parenthetical default URL is slightly redundant with the schema but does not harm readability.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-optional-parameter navigation tool with no output schema and no annotations, the description covers purpose, environment, and default destination. It still leaves the agent guessing about tab behavior and post-call state, which matters for chaining into read or click.

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

Parameters3/5

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

Schema coverage is 100% and the single url parameter is fully documented there, so the description's restatement of the default adds nothing new. It gives no format hints such as whether a path-relative URL versus an absolute URL is expected.

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?

Names a specific verb ("Open") and resource ("CoachingPortal page") plus the execution environment ("signed-in Cloud Browser"). This is clearly distinguishable from siblings like coachingportal_click, read, or type at the verb level, though it never explicitly contrasts itself with them.

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?

The clause "to work with review client check-ins and training programs" implies the domain where this tool applies, and "signed-in" hints at a prerequisite session state. There is no explicit when-to-use versus when-not guidance and no mention of sequencing relative to coachingportal_click, read, or status.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server