Eversports Studio Manager by Cotlet

Configure booking questions in Eversports Studio Manager

eversports_studio_manager_configure_booking_questions

Read-onlyIdempotent

Configure booking questions 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_configure_booking_questions"
  }
}

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=true, idempotentHint=true and destructiveHint=false, and the description reinforces this with 'opens nothing by itself'. It adds genuine context beyond the annotations: the return shape (step-by-step screens, buttons, fields) and why browser automation is required, because the official Provider API is read-only across eight areas and cannot add, change or cancel anything.

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 operative guidance is front-loaded, but the closing API paragraph is padded and partly self-repeating ('Eversports Studio Manager's official API: Eversports Studio Manager has an official Provider API'). Its rationale is useful, yet it could be stated in one clause rather than an enumerated list of eight read areas.

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 comes back (step-by-step instructions) and what to do next. Nothing essential to correct invocation is missing, and annotations carry the safety profile.

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 no parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. No parameter semantics are 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 names a specific verb and resource (configure booking questions) and scopes it to the user's own Eversports Studio Manager account. It also draws a clear line between this tool (returns step-by-step instructions, opens nothing by itself) and the cotlet_browser_* tools that carry out the change, which lets an agent separate it from ordinary action tools.

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 states the workflow explicitly: call this to get screens/buttons/fields, then execute with the cotlet_browser_* tools in the Cloud Browser. It gives no exclusions among the many sibling configure_* tools, so an agent must infer that each sibling handles a different settings area, but the when-to-use case is otherwise unambiguous.

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?