Gymdesk by Cotlet

Run Front Desk Mode in Gymdesk

gymdesk_run_front_desk_mode

Read-onlyIdempotent

Run Front Desk Mode in the user's own Gymdesk account from ChatGPT, Claude or any AI agent. Returns how to do it in Gymdesk step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Gymdesk Cloud Browser. Gymdesk's official API: No publicly documented Gymdesk API was found on 11 Nov 2026: gymdesk.com/api, gymdesk.com/developers and docs.gymdesk.com/api returned 404 and the help center has no Gymdesk API article.

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Beyond the readOnly/idempotent annotations, it discloses that nothing is opened or executed and that output is procedural text (screens, buttons, fields). That is meaningful behavioral context an agent would otherwise have to guess. It does not mention output size or formatting limits, which would have pushed it higher.

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 first sentence is front-loaded and useful, but the second crams three ideas together, and the third is a long digression listing 404 URLs and a search date for the official API. That API-availability detail explains the browser fallback but is over-specified for a tool description whose job is selection and invocation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 tool with annotations covering safety, most of what is needed is present: it says what comes back and what to do next. It never explains what 'Front Desk Mode' actually contains in Gymdesk, so an agent cannot judge whether this is the right entry point versus a more specific sibling.

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 and the schema is fully described, so the baseline of 4 applies. The description correctly adds nothing about inputs because there are none — the target account is implicitly the user's own, which is stated.

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 the resource (Front Desk Mode in the user's Gymdesk account) and crucially clarifies that it returns step-by-step instructions rather than performing the action: 'returns how to do it in Gymdesk step by step (screens, buttons, fields) and opens nothing by itself.' The verb 'Run' in the name is slightly misleading for a guidance-retrieval tool, but the body corrects that immediately.

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 gives a clear follow-on path — take the returned steps and execute them with cotlet_browser_* tools in the user's Cloud Browser — which tells an agent how to chain this tool. However, it never says when to choose this over the many sibling gymdesk_* tools, and it does not specify prerequisites such as whether a Gymdesk Cloud Browser session must already exist.

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

All Gymdesk 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?