Momence MCP Server and API by Cotlet

Book customer into class in Momence

momence_book_customer_into_class

Read-onlyIdempotent

Book customer into class in the user's own Momence account from ChatGPT, Claude or any AI agent. Returns how to do it in Momence step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Momence Cloud Browser. Momence's official API: Momence has a Developer API with OAuth 2.0 that reads members, classes and bookings, books free spots, checks in, cancels bookings and freezes memberships, but it has no endpoint to create or cancel classes, message customers, cancel renewals or refund payments (checked 11 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": "momence_book_customer_into_class"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A3.9/5.0

Behavior4/5

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

The annotations already declare readOnlyHint=true and destructiveHint=false, and the description reinforces this with 'opens nothing by itself' — important because the tool name sounds like a mutation. It also discloses the return shape (step-by-step screens, buttons, fields), which annotations and the absent output schema do not cover; error or edge-case behavior is not described.

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 clarification are front-loaded, but the trailing API-capability paragraph enumerates many endpoints (check-ins, freezes, cancellations) that are tangential to this tool, and 'from ChatGPT, Claude or any AI agent' is filler that does not help tool selection.

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 description covers what it returns, that it performs no action, and how to follow up with browser tools. It is essentially complete, though it says nothing about what happens if the user's account or the target class is not accessible.

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 there is no parameter meaning for the description to add or omit.

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?

The description names a specific resource and action (booking a customer into a class in the user's own Momence account) and then corrects the likely misreading by stating it returns step-by-step instructions rather than performing the booking. It does not explicitly contrast with siblings like momence_check_in_member or momence_create_class, so it falls short of a 5.

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?

It gives a clear workflow: use this tool to obtain screens/buttons/fields, then execute with the cotlet_browser_* tools in the Momence Cloud Browser, and it explains why the official API is not an option. It stops short of explicit when-not-to-use conditions or comparison against the sibling Momence action tools.

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

All Momence 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?