Gymdesk by Cotlet

Convert or invite lead to member in Gymdesk

gymdesk_convert_or_invite_lead_to_member

Read-onlyIdempotent

Convert or invite lead to member 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_convert_or_invite_lead_to_member"
  }
}

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 destructiveHint=false, but on their own they would leave ambiguous whether the tool reads lead records. The description resolves this by saying it 'opens nothing by itself' and returns instructions, and it explains why no API call happens. It does not describe the shape or length of the returned steps.

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 and the key non-action caveat are front-loaded, which is good. However, the opening phrase 'from ChatGPT, Claude or any AI agent' is promotional filler, and the closing URL-audit sentence (with a specific date and three 404 URLs) is disproportionately long for the value it adds.

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, no-output-schema guidance tool, the description covers what it returns, that it performs no mutation, and which tool family to use next. The only gap is that it never states the form of the returned steps (text vs structured) or any prerequisite that the Cloud Browser session must already exist.

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 there is nothing for the description to disambiguate; the baseline for a parameterless tool applies. The description correctly implies no input is needed because the output is guidance rather than a scoped query.

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?

States a specific verb and resource (convert or invite a lead to member) and, crucially, clarifies the deliverable: step-by-step Gymdesk instructions rather than an executed action. It does not name any sibling tool by name, so it does not fully differentiate from neighbours like gymdesk_add_or_quick_add_a_member_or_visitor or the bulk lead tools.

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 routes the agent: this tool yields the procedure, then the actual work is done with the cotlet_browser_* tools in the Gymdesk Cloud Browser. It also implicitly excludes API-based execution by noting no public Gymdesk API exists. It stops short of stating when a sibling (e.g. add/quick-add member) would be the better choice instead.

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?