Momence MCP Server and API by Cotlet

Freeze membership in Momence

momence_freeze_membership

Read-onlyIdempotent

Freeze membership 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_freeze_membership"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already establish that this is read-only, non-destructive, and idempotent, and the description adds important behavioral context: it returns step-by-step screens, buttons, and fields, and opens nothing by itself. That meaningfully clarifies that the tool is instructional rather than a mutating action. It does not describe return format beyond 'step by step,' but the annotations cover much of the safety profile.

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 behavior are front-loaded, but the description spends substantial space on Momence API capabilities and a checked date. That API detail is potentially confusing because it states the official API can freeze memberships, which is not clearly reconciled with using this instructional tool. The phrasing 'from ChatGPT, Claude or any AI agent' is also unnecessary for an agent already invoking the tool.

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 is returned (step-by-step screens, buttons, fields) and the next action (use cotlet_browser_* tools). It identifies the account context and the Cloud Browser. The main gap is not explaining why this tool should be used instead of the official API endpoint that the description says can freeze memberships.

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?

There are zero parameters and the schema is empty, so the baseline is 4. The description does not need to explain parameter semantics, and no parameter-related meaning is missing.

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 states that the tool returns step-by-step instructions for freezing a membership and clarifies that it opens nothing by itself. It also distinguishes the tool from the cotlet_browser_* tools that actually perform the action. The initial wording 'Freeze membership...' and the name create slight tension with the later clarification that it only returns instructions, so it is not a perfect 5.

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?

The description tells the agent to use this tool to obtain steps and then use cotlet_browser_* tools in the user's Momence Cloud Browser. However, it does not explicitly say when to use this instructional tool rather than the official Momence API, especially since the description notes that the official API can freeze memberships. It implies usage but lacks clear when/when-not guidance or named alternatives.

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?