Eversports Studio Manager by Cotlet

Bulk extend activities in Eversports Studio Manager

eversports_studio_manager_bulk_extend_activities

Read-onlyIdempotent

Bulk extend activities 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_bulk_extend_activities"
  }
}

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?

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, and the description is consistent with that, reinforcing that the tool performs no side effects. It adds useful behavior beyond the annotations by explaining the output is procedural guidance and that execution happens via a separate browser-tool step, though it says nothing about output size, failure modes, or rate limits.

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 no-side-effect behavior are front-loaded, which is good, but the definition spends a full sentence on marketing-flavored framing ('from ChatGPT, Claude or any AI agent') and a lengthy aside on the official Provider API being read-only. That API detail is tangential to invoking this tool and dilutes the core instruction.

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 parameters and no output schema, the description carries the burden of explaining what comes back, and it does so by stating the return is step-by-step screens/buttons/fields and that the browser tools execute the action. Complete enough to call correctly, with only minor gaps around result format detail.

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 schema baseline is 4 and there is no parameter meaning the description could add. Nothing is missing or misrepresented on this dimension.

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 verb and resource (bulk extend activities) scoped to the user's own Studio Manager account, which is clear enough for an agent to identify the operation. It does not explicitly contrast with sibling operations such as bulk_cancel_appointments, and 'extend activities' itself is only loosely defined, leaving some ambiguity about what is being extended.

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 clearly states that the tool only returns step-by-step instructions (screens, buttons, fields) and 'opens nothing by itself,' then tells the agent to perform the action with the cotlet_browser_* tools in the Cloud Browser. That is real workflow guidance, but it offers no explicit when-to-use/when-not comparison against sibling tools.

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?