Skip to main content
Glama

Add a new location to the account in Gymdesk

gymdesk_add_a_new_location_to_the_account
Read-onlyIdempotent

Add a new location to the account 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_add_a_new_location_to_the_account"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, and the description is consistent with them: 'opens nothing by itself' removes the risk of an agent reading the name as a write operation. It also discloses the return content (step-by-step screens, buttons, fields), which goes beyond what the annotations state. It stops short of describing length or formatting of the returned guide.

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 opening clause and the 'opens nothing by itself' correction are front-loaded and earn their place. The trailing research note about Gymdesk's API returning 404 is long and only indirectly relevant, justifying why the tool is a how-to rather than an API call, and could be compressed considerably.

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 parameters and no output schema, the definition covers what is returned and what to do next. It omits prerequisites that matter for a location-creation task, such as required permission level or plan limits, leaving the agent to discover those from the returned guide.

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 schema carries no semantics to supplement and the baseline is 4. The description correctly implies no inputs are needed beyond knowing which location to add.

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 states a specific verb and resource (add a location to the account) and then sharpens it: it returns step-by-step instructions (screens, buttons, fields) rather than performing the change. This distinguishes it well from the operational siblings like gymdesk_add_or_quick_add_a_member_or_visitor, though the name alone would mislead without that clarification.

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 tells the agent the follow-up path explicitly: use the cotlet_browser_* tools in the user's Gymdesk Cloud Browser to actually create the location. It does not state exclusions (e.g., when to skip this and use a different research/how-to tool), but the workflow context is clear.

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