Eversports Studio Manager by Cotlet

Create sepa mandate in Eversports Studio Manager

eversports_studio_manager_create_sepa_mandate

Read-onlyIdempotent

Create sepa mandate 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_create_sepa_mandate"
  }
}

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 and idempotentHint=true; the description reinforces this by stating it 'opens nothing by itself' and describes the return content (step-by-step screens/buttons/fields). It also explains the follow-up execution path via browser tools. A minor gap is that it does not name the exact return structure, but the behavioral picture is strong.

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 is front-loaded, but the middle sentence is dense and the closing sentence about the official Provider API being read-only, while relevant context, is somewhat tangential and wordy. It could be tightened 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 guide-style tool with no output schema, the definition explains what it returns, that it is non-mutating, and how to proceed afterward with the browser tools. The read-only API note frames the constraints. It is nearly complete, though the exact format of the returned steps remains unspecified.

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?

There are zero parameters, so the baseline is 4. The description does not need to explain any parameter semantics, and the empty schema is consistent with the described behavior. No extra parameter meaning is required or 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 states a specific verb and resource (create a SEPA mandate) in the user's own Studio Manager account, and then carefully reframes what the tool actually does: returns step-by-step instructions (screens, buttons, fields) without opening anything. This disambiguates the potentially misleading name. It does not explicitly name a sibling it is contrasted with, which keeps it from 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 Guidelines4/5

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

Usage context is clear: it is meant to be used from any AI agent, and after obtaining the steps the agent should execute them with the cotlet_browser_* tools in the Cloud Browser. The note that the official Provider API is read-only implicitly explains why this guide-plus-browser path is necessary. Explicit exclusions or named sibling alternatives are absent.

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?