Eversports Studio Manager by Cotlet

Edit appointments in Eversports Studio Manager

eversports_studio_manager_edit_appointments

Read-onlyIdempotent

Edit appointments 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_edit_appointments"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, but the description adds genuinely non-obvious context: the tool opens nothing itself, it returns a procedural walkthrough, and the follow-up must happen in the Cloud Browser. It also explains that the official Provider API is read-only across eight areas, which justifies why browser automation is needed. Missing details on auth/session prerequisites keep it at 4.

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 mechanism are front-loaded and clear, but the text is repetitive ("Eversports Studio Manager" appears five times) and the final API sentence is long and tangential to invoking this tool. Trimming would improve scanability without losing meaning.

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 guidance tool, the description covers what is returned (screens, buttons, fields), what is not done (nothing is opened or changed), and how to complete the action. A note on which appointment types or required account state would make it fully complete.

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 the baseline is 4. The description introduces no parameter-level content, which is correct here since the tool takes no arguments and all targeting happens in the subsequent browser step.

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 ("Edit appointments in the user's own Eversports Studio Manager account") and immediately clarifies the actual function is to return step-by-step instructions rather than perform the edit. It does not name or differentiate against sibling edit/cancel tools, so it stops 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides a clear workflow: call this to get screens/buttons/fields, then execute via the cotlet_browser_* tools in the Cloud Browser. However, it gives no when-not guidance and no routing among siblings such as cancel_a_single_appointment or bulk_cancel_appointments_with_optional, leaving the agent to infer which appointment-editing tool fits.

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?