Skip to main content
Glama

Create a Point-of-Sale sale in Gymdesk

gymdesk_create_a_point_of_sale_sale
Read-onlyIdempotent

Create a Point-of-Sale sale 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_create_a_point_of_sale_sale"
  }
}

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 declare readOnlyHint=true and destructiveHint=false; the description reinforces this with 'opens nothing by itself' and adds genuinely new information about what is returned (screens, buttons, fields). The note that no public Gymdesk API exists explains why browser automation is required, which is useful behavioral context not present in the annotations.

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 core behavior is front-loaded, which is good, but the description is a single run-on sentence that crams the instruction-return behavior, the browser-tool handoff, and a lengthy API-404 research note together. The final sentence about 404s at gymdesk.com/api and docs.gymdesk.com/api is verbose relative to its value.

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 no output schema, the description correctly compensates by describing the return value as step-by-step screens, buttons, and fields. Given zero parameters and straightforward annotations, that is nearly everything an agent needs, though it could state whether the guidance is specific to a POS workflow variant (in-person sale vs. product/variant selection).

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 the baseline applies and there is nothing for the description to disambiguate. The schema is fully closed (additionalProperties: false) and requires no explanation.

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 first sentence names a specific verb and resource (create a Point-of-Sale sale) and immediately clarifies the actual mechanic: it returns step-by-step Gymdesk instructions rather than performing the action. That distinction is essential and well stated, though the framing still leads with a name that sounds like a write operation, so an agent must read the second clause to understand what it really does.

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?

The description gives a clear workflow context: call this to get the click-path, then execute with the cotlet_browser_* tools in the user's Gymdesk Cloud Browser. It does not state when NOT to use it or point to related sibling tools (e.g. refund_a_sale_or_cancel_a_manual_sale or create_a_one_time_charge_for_a_member) for adjacent tasks, so routing among siblings is only partially aided.

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