Mariana Tek MCP Server and API by Cotlet

Book reservation in Mariana Tek

mariana_tek_book_reservation

Read-onlyIdempotent

Book reservation in the user's own Mariana Tek account from ChatGPT, Claude or any AI agent. Returns how to do it in Mariana Tek step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Mariana Tek Cloud Browser. Mariana Tek's official API: Yes, but gated: Mariana Tek has APIs (Customer, Studio, Admin, Webhooks and more), and credentials go only to integration partners who sign the Developer Tools Terms of Service and to developers working with a single studio, with the studio owner included in the request; no official MCP server exists (checked 11 Oct 2026).

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": "mariana_tek_book_reservation"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A3.7/5.0

Behavior4/5

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

The description adds meaningful context beyond the readOnly/idempotent annotations: it explains that the tool is purely instructional and opens nothing by itself, that a browser session in Mariana Tek is required, and that the official API is gated behind partner terms with no MCP server. It omits what the step-by-step output looks like in detail, but the key behavioral trait (non-executing guidance) is disclosed clearly and does not conflict with readOnlyHint=true.

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 essential instruction is front-loaded, but the final sentence on Mariana Tek's API gating and the dated parenthetical is long and mostly justification rather than actionable guidance for invoking the tool. The core workflow could be stated in one tight sentence.

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, non-destructive guidance tool with full annotation coverage and no output schema, the description covers purpose, the follow-up browser requirement, and why no API alternative exists. A brief note on prerequisites (e.g. being logged in) would make it 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?

There are zero parameters, so the baseline is 4; the description correctly implies no inputs are needed when booking and specifies the target account (the user's own). It does not explain why no studio/class identifier is accepted, which is the main semantic gap.

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 ("Book reservation in the user's own Mariana Tek account") and clarifies that the tool itself opens nothing, distinguishing it from the cotlet_browser_* tools. It does not explicitly contrast with mariana_tek_cancel_reservation or mariana_tek_list_classes, but the booking intent is unambiguous.

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?

It implies the workflow: call this first to get step-by-step instructions, then perform the booking with cotlet_browser_* tools in the Cloud Browser. However, it never states when not to use this tool, nor does it point to siblings like list_classes for discovering classes before booking, leaving the sequencing partially inferred.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Mariana Tek MCP Server and API 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?