Skip to main content
Glama

View the gym schedule and session participants in Gymdesk

gymdesk_view_the_gym_schedule_and_session_participants
Read-onlyIdempotent

View the gym schedule and session participants 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_view_the_gym_schedule_and_session_participants"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover readOnlyHint, idempotentHint, destructiveHint and openWorldHint=false, and the description stays consistent with them by stressing that nothing is opened or executed. It adds genuinely useful context — that the return value is procedural guidance (screens, buttons, fields) and that a separate browser toolchain performs the action — though it does not describe the shape or granularity of that guidance.

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 operative content is front-loaded and useful, but the opener 'from ChatGPT, Claude or any AI agent' is filler, and the closing API paragraph (dated 404 checks on gymdesk.com/api, /developers, docs.gymdesk.com/api and the help center) is long evidentiary justification rather than agent-actionable guidance. A shorter statement that no public API exists would serve the same purpose.

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 helper, the definition covers what the tool returns, that it performs no action, and which tools must follow it. Missing only minor practical detail such as prerequisites (signed-in session, account permissions) before handing off to the browser tools.

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 schema declares zero parameters with additionalProperties false, so there is nothing for the description to disambiguate. The baseline of 4 applies; the description properly adds no parameter claims that could conflict.

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 resource (gym schedule and session participants) and, importantly, clarifies the real output: step-by-step instructions covering screens, buttons and fields rather than the data itself. That correction is buried in the second sentence, so the leading 'View ... in the user's own Gymdesk account' still reads like a data-retrieval tool at first glance.

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?

It explicitly states this tool 'opens nothing by itself' and that the actual work must be done with the cotlet_browser_* tools in the Gymdesk Cloud Browser, which is a clear use/no-use boundary. It does not differentiate against siblings such as gymdesk_edit_cancel_or_delete_a_session or the reporting tools, but the guidance-to-browser pairing is stated concretely.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources