ClassPass MCP Server and API by Cotlet

List class roster in ClassPass

classpass_list_class_roster

Read-onlyIdempotent

List class roster 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_class_roster"
  }
}

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?

The annotations already declare read-only, idempotent, non-destructive and closed-world, and the description reinforces rather than repeats them by stating it "opens nothing by itself." It adds genuinely new behavioral context: the return is procedural screens/buttons/fields, and the actual action requires the browser tools. It does not cover permissions (e.g. host/owner role needed to view a roster), which would have pushed this higher.

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-loaded with the purpose, then the actual behavior, then the follow-up workflow and API rationale — a sensible order. The closing API sentence with its "checked 28 Oct 2026" stamp is somewhat extraneous for an invocation decision, though it does preempt an agent from trying the official API.

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 no output schema, the description carries the return-value burden and does so ("step by step (screens, buttons, fields)"), plus it names the tools needed to act on that output. For a zero-parameter instruction tool this is close to complete; only the permission prerequisites for viewing a roster 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, and the description correctly implies no input is required by describing a parameterless instruction lookup. There is no meaningful additional parameter context it could add.

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 class roster in the user's own ClassPass account") and immediately clarifies the real behavior: it returns a step-by-step guide rather than data. That correction is valuable, but the description never distinguishes it from nearby siblings such as classpass_list_reservations or cotlet_app_guide, so the agent must infer the boundary.

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 a clear operating context: call this to get instructions, then execute with the cotlet_browser_* tools in the ClassPass Cloud Browser. It also explains why the official ClassPass Inventory API is not an option, which justifies the browser route. It stops short of explicit when-not-to-use guidance against the other classpass_* tools.

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?