Skip to main content
Glama

update_gym_class

Replace a recurring class's definition (confirm-gated). Sends every field — read list_gym_classes first.

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": {
      "classId": "<classId>",
      "title": "<title>",
      "capacity": "<capacity>",
      "durationMinutes": "<durationMinutes>",
      "weekdays": "<weekdays>",
      "startTime": "<startTime>"
    },
    "name": "update_gym_class"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYes
classIdYes
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
durationMinutesYes
instructorCoachIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only cover the read-only/open-world/destructive triad; the description adds two real behavioral facts beyond them: the operation is confirm-gated (preview by default) and it is a whole-object send. "Sends every field" is the key disclosure, warning that unspecified optional fields are not preserved — behavior an agent could easily get wrong. It stops short of saying what happens to already-scheduled sessions or rosters.

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, zero filler, with the core operation and the confirm gate front-loaded before the prerequisite read. Nothing is redundant with the schema beyond what is necessary to set up the "sends every field" warning.

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?

For an 11-parameter, non-read-only replacement of a recurring class with no output schema, the definition covers the gate, the full-send semantics, and the prerequisite read — the essentials for calling it. It omits the operational consequences that matter most here: the effect on existing sessions, rosters, or bookings, and whether omitted optional fields are cleared or retained.

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?

Schema description coverage is only 36%, so the description must compensate, and it partially does by establishing that all fields are sent at once (no partial update). However, with 11 parameters — including undocumented ones like locationId, instructorCoachId, capacity, and description — there is no per-parameter guidance on the reset semantics or valid combinations.

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?

"Replace a recurring class's definition" gives a specific verb (replace, not update) plus the resource, and the parenthetical flags the confirm gate. The deliberate use of "Replace" is meaningful because it distinguishes a full overwrite from an incremental edit. It does not explicitly contrast with siblings like create_gym_class or deactivate_gym_class, which keeps it from a 5.

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 supplies one concrete workflow rule: "read list_gym_classes first," which tells the agent to gather IDs before calling. Beyond that, usage is only implied — there is no statement of when to choose this versus create_gym_class, deactivate_gym_class, or the standing/session tools. Adequate but with a clear gap.

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.