Exercise.com by Cotlet

Cancel a session / appointment in Exercise.com

exercise_com_cancel_a_session_appointment

Read-onlyIdempotent

Cancel a session / appointment in the user's own Exercise.com account from ChatGPT, Claude or any AI agent. Returns how to do it in Exercise.com step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Exercise.com Cloud Browser. Exercise.com's official API: Exercise.com has an official API as a paid add-on: "API access is an additional feature with variable pricing", quoted by your Account Representative for your intended usage (checked 11 Nov 2026).

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": "exercise_com_cancel_a_session_appointment"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description reinforces this by stating the tool "opens nothing by itself" and only returns instructions, which resolves the apparent tension of a "cancel" tool being read-only. It also discloses the required follow-up mechanism (cotlet_browser_* in the user's Cloud Browser), which is genuine context beyond the annotations. It does not cover what happens if the session cannot be cancelled or any cancellation-policy constraints.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core purpose and the read-only/next-step clarification are front-loaded and earn their place. The trailing paragraph about Exercise.com's official API pricing is boilerplate that does not help an agent decide or invoke this tool, and it dilutes an otherwise tight definition.

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?

With zero parameters and no output schema, the description carries the burden of explaining the return value, which it does (step-by-step screens, buttons, fields). Combined with annotations covering the safety profile, an agent has enough to call it correctly; only edge-case behavior (ineligible appointments, policy limits) is unaddressed.

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 the baseline is 4; there is nothing for the description to disambiguate. No parameter meaning is lost.

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 ("Cancel a session / appointment") and scopes it to "the user's own Exercise.com account," then immediately clarifies the tool only returns instructions rather than performing the cancellation. It does not name which sibling to use instead for a reschedule or no-show, but the action itself is unambiguous.

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?

Provides a usable workflow: call this to get step-by-step screens/buttons/fields, then execute with cotlet_browser_* tools in the Cloud Browser. However, it gives no guidance on when to prefer this over sibling flows such as rescheduling a session or processing a late cancel/no-show, and no prerequisites or exclusions are stated.

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

All Exercise.com 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?