ClassPass MCP Server and API by Cotlet

List reservations in ClassPass

classpass_list_reservations

Read-onlyIdempotent

List reservations 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_list_reservations"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the bar is low; the description still adds real value by saying it returns step-by-step screens/buttons/fields and opens nothing itself. The note that the official ClassPass Inventory API is partner-only explains why browser automation is the path, which usefully frames the agent's next move.

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?

Purpose and the no-side-effect guarantee are front-loaded, and the sentence order matches the agent's decision sequence. The "from ChatGPT, Claude or any AI agent" clause and the dated API note are slightly extraneous but still serve to justify the browser-based workflow.

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, read-only guidance tool with no output schema, the definition covers what it returns, what it does not do, and how to continue. Only the exact shape of the returned instructions (text vs. structured steps) is left implicit.

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 schema has zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. No parameter documentation is needed or 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?

States a specific verb and resource ("List reservations in the user's own ClassPass account") and immediately discloses that the tool returns procedural guidance rather than data. The scope qualifier "user's own" separates it from account-wide reporting siblings, though no sibling is named explicitly.

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 workflow context: call this, then perform the action with cotlet_browser_* tools, and notes it "opens nothing by itself." It stops short of explicit exclusions — it never says when to use classpass_get_reservation_report or other reservation siblings instead.

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?