Mariana Tek MCP Server and API by Cotlet

Cotlet: how to work in an app

cotlet_app_guide

Read-onlyIdempotent

How to work in an app by clicking in the user's Cloud Browser with Cotlet's browser tools: which browser to use for this workspace and the sign-in link, the method step by step, the app's screens, menus and actions, notes, and the app's dedicated tools when Cotlet has them. Call it before the first browser step in an app. Works for any web app; one outside Cotlet's catalog gets the general method. Free, no browser session. For Mariana Tek it covers these actions: List classes, Book reservation, Cancel reservation, Find customer, Add class credits.

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

Input Schema

Name	Required	Description	Default
`app`	No	The app's name or Cotlet slug. Default: Mariana Tek.
`task`	No	What the user wants done in the app, in their words.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely new context beyond them: "Free, no browser session" tells the agent this costs nothing and consumes no browser tab, and the enumerated return contents reveal what the guide yields.

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 opening sentence is a long run-on list of everything the guide contains, which delays the core instruction. The subsequent short sentences ("Call it before the first browser step in an app", "Free, no browser session") are efficient and carry real value, but the front-loading is weak.

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 only two optional parameters, no output schema, and no nesting, the description supplies enough: what it returns, when to call it, and that it is free and sessionless. Explaining return values further is unnecessary absent an output schema, so this is close to complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, with both `app` (default Mariana Tek) and `task` documented in the schema, so the description is not required to compensate. The line "For Mariana Tek it covers these actions: ..." indirectly hints at what a task can express but does not explain either parameter directly, matching the baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource precisely: a guide covering which browser to use, the sign-in link, the step-by-step method, screens/menus/actions, notes, and any dedicated app tools. It also distinguishes itself from the browser_* and app-specific siblings by saying it returns guidance, not the browser actions themselves.

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?

"Call it before the first browser step in an app" gives explicit sequencing guidance, and "Works for any web app; one outside Cotlet's catalog gets the general method" sets expectations for coverage. It stops short of naming a sibling alternative or stating a when-not condition, which keeps it out of the top band.

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?