ClassPass MCP Server and API by Cotlet

Cancel reservation in ClassPass

classpass_cancel_reservation

Read-onlyIdempotent

Cancel reservation in the user's own ClassPass account from ChatGPT, Claude or any AI agent. Returns how to do it in ClassPass step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's ClassPass Cloud Browser. ClassPass's official API: ClassPass has an official API, the ClassPass Inventory API, but only approved partners can use it (checked 28 Oct 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": "classpass_cancel_reservation"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A4.3/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 rather than repeats them by stating it 'opens nothing by itself' — the key non-obvious behavior for a tool named 'cancel'. It also discloses that the vendor API is inaccessible to this tool. No rate limits or failure modes described, but there is little dynamic behavior to disclose. No contradiction: the name implies mutation, but the description makes clear the tool only returns instructions, consistent with readOnlyHint=true.

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-loads the action and the crucial 'returns instructions, opens nothing' caveat in the first two sentences. The closing sentence on the official API is relevant but slightly tangential, and 'from ChatGPT, Claude or any AI agent' is promotional filler that could be trimmed.

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 with full annotation coverage, the description covers what it is, what it returns (step-by-step screens/buttons/fields), and the follow-up path. Missing only guidance on what the returned guide looks like structurally or what to do if the steps don't match the user's UI.

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?

Zero parameters, so semantics are trivially complete; schema coverage is 100% and the description adds no parameter claims to conflict. Baseline for a 0-param tool.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb and resource (cancel a reservation in the user's own ClassPass account) and immediately disambiguates the non-obvious part: this tool does not perform the cancellation, it returns a step-by-step guide. That distinction separates it cleanly from siblings like classpass_list_reservations and from the cotlet_browser_* executor tools.

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?

Explicitly routes the agent: use this to obtain the screens/buttons/fields, then execute with cotlet_browser_* in the ClassPass Cloud Browser. It also explains why the official API is not an option (approved partners only). It stops short of stating preconditions or when-not-to-use cases (e.g., reservation already cancelled, user not signed in).

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

All ClassPass MCP Server and API 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?