Gymdesk by Cotlet

Mass check-in members to a session in Gymdesk

gymdesk_mass_check_in_members_to_a_session

Read-onlyIdempotent

Mass check-in members to a session 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_mass_check_in_members_to_a_session"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A3.8/5.0

Behavior5/5

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

Given readOnlyHint=true, the description explains exactly why: the tool returns a procedure and 'opens nothing by itself', so the agent knows the actual mutation must happen through the browser tools. It also discloses the fallback rationale (no documented Gymdesk public API), which prevents an agent from attempting a direct API path instead.

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 read-only-then-browser-tools behavior are front-loaded and earn their place. The trailing paragraph about 404s on gymdesk.com/api and the help center is verbose for a two-line justification and reads like research notes rather than operational guidance.

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?

With no input schema and no output schema, the description must carry the full burden, and it does explain what comes back (ordered screens/buttons/fields). What it omits is how the agent is supposed to know which session and which members get checked in, which is the key missing piece for actually driving the flow.

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 at the argument level; baseline 4 applies. The unspecified session/member targeting is a usage gap rather than a parameter-semantics one.

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 names a specific verb and resource (mass check-in members to a session) and states what is returned: step-by-step screens, buttons and fields. It does not explicitly differentiate from the singular sibling gymdesk_check_a_member_visitor_or_lead_in_to_a_session, so the 'mass' qualifier does the distinction work implicitly.

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 usable flow — call this for instructions, then execute with the cotlet_browser_* tools in the user's Gymdesk Cloud Browser — and clarifies that the tool performs no action. However, it never specifies how the target session or the member set is identified, and gives no guidance on when to prefer this over the single-member check-in sibling.

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?