Skip to main content
Glama

Configure attendance settings and membership cards in Gymdesk

gymdesk_configure_attendance_settings_and_membership_cards
Read-onlyIdempotent

Configure attendance settings and membership cards 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_configure_attendance_settings_and_membership_cards"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false. The description reinforces this by stating it 'opens nothing by itself' and that execution happens through browser tools, which is useful confirmation rather than new information. It also discloses that no public Gymdesk API exists, explaining why the browser path is required, but says nothing about output format or limits of the generated instructions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded in the first clause, followed by the behavioral caveat and then the API justification. The closing note about 404s on three specific URLs is slightly verbose but does earn its place by justifying the browser-based workflow.

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 zero parameters and no output schema, the definition covers what the agent needs: what is returned (step-by-step screens, buttons, fields) and what must happen next (cotlet_browser_* tools). Only the granularity/format of the returned instructions is left unspecified, which is a minor gap.

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?

The tool takes zero parameters and schema coverage is 100%, so the baseline applies. The description adds that no input is expected because the tool only emits guidance, but there are no parameter semantics to enrich.

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 set (attendance settings and membership cards) and a specific delivery mode (returns step-by-step screens/buttons/fields). It is clear what the tool produces, though it does not distinguish this configure tool from the many sibling gymdesk_configure_* tools (booking, member, billing, marketing).

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 concrete usage pattern: call this to get instructions, then execute them with cotlet_browser_* tools in the Gymdesk Cloud Browser, and it explicitly says the tool opens nothing itself. What it lacks is any routing guidance against the sibling configure_* tools, so an agent must infer whether attendance/membership-card settings belong here or in gymdesk_configure_member_settings_*.

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