Eversports Studio Manager by Cotlet

Edit sold entitlement in Eversports Studio Manager

eversports_studio_manager_edit_sold_entitlement

Read-onlyIdempotent

Edit sold entitlement 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_sold_entitlement"
  }
}

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?

Goes beyond annotations by disclosing the return shape (screens, buttons, fields) and the key non-effect ('opens nothing by itself'), which is consistent with readOnlyHint=true and destructiveHint=false. Missing details on length/format of the returned steps are minor given how short the tool's job is.

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 sentence is front-loaded and useful, but the closing API paragraph is longer than needed and repeats the full product name several times, adding bulk without much decision value.

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, no output schema and a simple advisory role, the description covers what the tool does, what it returns, and what it does not do. A brief note on how the returned steps map to the browser tool inputs 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 tool takes zero parameters, so the baseline is 4; the description correctly frames the tool as needing no input beyond the request itself.

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?

Names a specific verb and resource ('Edit sold entitlement') and immediately clarifies the actual behavior: it returns step-by-step UI instructions rather than performing the edit. This distinguishes it from a mutation tool, though the domain term 'sold entitlement' is left unexplained.

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?

Explicitly states the follow-up path ('do it with the cotlet_browser_* tools in the user's ... Cloud Browser') and rules out the official Provider API by explaining it is read-only. It does not explicitly say when to pick this over the many sibling edit tools, but the routing to browser tools is clear.

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?