Skip to main content
Glama

create_gym_class

Create a recurring gym class (confirm-gated). Members can then book its sessions.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "organizationId": "<organizationId>",
      "title": "<title>",
      "capacity": "<capacity>",
      "durationMinutes": "<durationMinutes>",
      "weekdays": "<weekdays>",
      "startTime": "<startTime>"
    },
    "name": "create_gym_class"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYes
confirmNoMust be true to actually execute. If false/omitted, returns a preview only.
capacityYes
timezoneNoIANA name, e.g. Asia/Kolkata
weekdaysYes0 = Sunday … 6 = Saturday
startTimeYesHH:mm, in the class timezone
locationIdNo
descriptionNo
organizationIdYes
durationMinutesYes
instructorCoachIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds genuine behavioral context: execution is gated behind confirmation and the created class becomes bookable by members. It omits permission/auth requirements and what the preview response contains.

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

Conciseness5/5

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

Two short sentences, front-loaded with the verb, resource, and the confirmation constraint. Nothing is padded or redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 11-parameter, 6-required creation tool with no output schema and low schema coverage, the description is thin: it never covers required identifiers, timezone handling for the recurring schedule, or what the preview returns. An agent could call it, but would be guessing on several required fields and on the shape of the confirm-gated response.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 36% across 11 parameters, so the description carries real burden here, yet it explains no parameter beyond restating the confirm gate that the schema already documents. Undocumented fields such as locationId, instructorCoachId, and description get no meaning from the description at all.

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?

States a specific verb and resource ('Create a recurring gym class') and adds the important qualifier that it is recurring rather than one-off. It does not distinguish itself from the sibling create_gym_class_standing, which an agent might reasonably confuse with a recurring-class creator.

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?

The '(confirm-gated)' note implies a preview-then-confirm flow, which is real usage guidance, and 'Members can then book its sessions' hints at the downstream purpose. However, there is no explicit when-to-use vs. when-not-to-use statement and no guidance on choosing between this and the standing/update siblings.

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.