Eversports Studio Manager by Cotlet

Pause membership in Eversports Studio Manager

eversports_studio_manager_pause_membership

Read-onlyIdempotent

Pause membership in the user's own Eversports Studio Manager account from ChatGPT, Claude or any AI agent. Returns how to do it in Eversports Studio Manager step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Eversports Studio Manager Cloud Browser. Eversports Studio Manager's official API: Eversports Studio Manager has an official Provider API, but it is read-only: it reads eight areas (business and venues, schedules, booking details, teachers, products, customers, customer products, and attendance and court bookings) and cannot add, change or cancel anything.

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": "eversports_studio_manager_pause_membership"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, and the description stays consistent while adding real value: it explains that the tool returns screens/buttons/fields instructions, performs no action, and requires a separate browser tool to execute. The explanation that the official Provider API is read-only justifies why a guide-only tool exists, though return shape and any auth/session prerequisites are only loosely 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 purpose and the 'returns instructions, opens nothing' caveat are front-loaded, which is good. However, the trailing API paragraph enumerating eight readable areas is long and largely tangential to invoking this tool, diluting the actionable content.

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 guide tool, the description covers what comes back (step-by-step screens, buttons, fields) and what the agent must do next. It falls short only on the precise return format and any preconditions for the follow-up browser session.

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 the description needs to compensate for. Nothing in the description misleads about inputs.

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 gives a specific verb and resource ('Pause membership in the user's own Eversports Studio Manager account') and immediately clarifies the unusual mechanic: it returns step-by-step instructions rather than acting. It does not name a sibling such as terminate_a_membership to contrast against, so the agent must infer why 'pause' differs from 'terminate'.

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?

Clear workflow context is supplied: this tool produces instructions and 'opens nothing by itself', after which the agent should act 'with the cotlet_browser_* tools in the user's ... Cloud Browser'. What is missing is any exclusion or alternative routing (e.g., when to prefer terminate or assign membership instead).

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

All Eversports Studio Manager 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?